Originally Posted By: ags
This new version surely resolves the orphan position case, but does it also resolves the OutOfMemory issue we experienced before? Have you also seen this or is it related to my overall system?

I've not experienced the OutOfMemory issue, but acctually I've not tested it with Z12, like you did.

Originally Posted By: ags
The connection is working on both directions, any idea what the difference could be?

I think they are the same. They recommend to change the connection url to http://platform.dukascopy.com/live_3/jforex_3.jnlp, but in the code example below the live address is:

Code:
// url of the LIVE jnlp
private static String jnlpUrl = "http://platform.dukascopy.com/live/jforex.jnlp";


Originally Posted By: ags
Got following messages today in the morning, after that the system remained connected and is working propperly. Any idea?

This exception indicates that the given communication channel was closed, for instance if the connection was reset by the server or a proxy.