Custom Query (172 matches)

The Log says:

14:31:21,470 ERROR  Command Line: -o F:\WORK\test.pdf -f F:\WORK\Unbenan2.pdf -f F:\WORK\Unbenan3.pdf -u All:All: -overwrite -pdfversion 3 concat
org.pdfsam.console.exceptions.console.ConcatException
	at org.pdfsam.console.business.pdf.handlers.ConcatCmdExecutor.execute(ConcatCmdExecutor.java:228)
	at org.pdfsam.console.business.pdf.CmdExecuteManager.execute(CmdExecuteManager.java:97)
	at org.pdfsam.console.business.ConsoleServicesFacade.execute(ConsoleServicesFacade.java:75)
	at org.pdfsam.guiclient.commons.business.WorkThread.run(WorkThread.java:43)
	at org.pdfsam.guiclient.commons.business.WorkExecutor$WorkQueue$PoolWorker.run(WorkExecutor.java:142)
Caused by: ExceptionConverter: java.io.IOException: close failed (Invalid handle)
14:31:21,550 WARN   Fehler beim Abspielen des Klangs: mark/reset not supported

​http://heanet.dl.sourceforge.net/project/pdfsam/pdfsam/2.2.1/pdfsam-2.2.1-out.zip

Reproduce:

1. Open App 2. Plugins Merge/Extract? 3. Add some PDFs 4. enter Dest-file 5. Run

See output in log below.

I have merged with PDFSAM some months ago with RC or beta, but RC/RC2 or Beta do now have the same problem.

Using a Java 6 environment and the latest ODIN, iTrain (Model Railroad Layout Control application, ​http://berros.eu/itrain/en/) was crashing every time a Drag & Drop action was done between different application windows. The debug log files pointed out that PMCTLS.DLL was involved. Finally we found out that the DragText? application of Rich Walsh was the culprit. Deinstallation of DragText? solved the Drag and Drop issues in iTrain. Question: is it possible to fix somehow that PMCTLS.DLL issue.

Java 6 still feels a quite a bit slow (in some areas). To demonstrate it, I used Jeti/2, measuring time from starting it and until GUI is up and roster and 4 MUCs (2 on local server 2 on remote) are populated.

All tests done from same client PC, only the loaded Java versions are different.

Jabber server Java 6 on eCS

Time to start Jeti/2 until roster and 4 MUC are filled

Java 1.41 | Java 1.42 | Java 1.50 | Java 1.60 |

| | | |

9 secs | 20 secs | 45 secs | 35 secs | 9 secs | 15 secs | 35 secs | 25 secs | 9 secs | 25 secs | 38 secs | 33 secs | 9 secs | 16 secs | 30 secs | 24 secs |

| | | |

1) 2) 3) 4)

(A lot more tests was actually done - these are the best results)

1) Java 1.41 loads in 9 secs in almost every test done.

2) Between 15-25 secs in mosts test. Not easy to see any specific

slow part.

3) Has seems to have some timing issues with sockets / DNS - hang

for a long time in same place.

4) Lots of tests were over 1 minut to load. Splash screen is

visible slowly drawn in parts. Communication with server seems to take a long time.

There seems to be room for improvement - although it may be hard to compete with our native 1.41