Hello Support,
I'm running the platform(2.43.2) and API(2.12.6) release.
When I try to login with multiple threads, then sometimes these related exceptions occur:
java.io.IOException: Client not online
at com.dukascopy.dds4.transport.client.TransportClient.controlRequest(TransportClient.java:557)
at com.dukascopy.dds4.transport.client.TransportClient.controlRequest(TransportClient.java:455)
at com.dukascopy.dds4.transport.client.TransportClient.controlRequest(TransportClient.java:517)
at com.dukascopy.api.impl.connect.DCClientImpl.connectedInit(DCClientImpl.java:700)
at com.dukascopy.api.impl.connect.DCClientImpl.authorized(DCClientImpl.java:990)
at com.dukascopy.dds4.transport.client.events.AuthorizedEvent.execute(AuthorizedEvent.java:23)
at com.dukascopy.dds4.transport.common.mina.EventTask.run(EventTask.java:35)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
After that there is always this:
java.io.IOException: Client not online
at com.dukascopy.dds4.transport.client.TransportClient.controlRequest(TransportClient.java:557)
at com.dukascopy.dds4.transport.client.TransportClient.controlRequest(TransportClient.java:455)
at com.dukascopy.dds4.transport.client.TransportClient.controlRequest(TransportClient.java:517)
at com.dukascopy.api.impl.connect.DCClientImpl$11.run(DCClientImpl.java:1227)
at com.dukascopy.api.impl.connect.DCClientImpl$11.run(DCClientImpl.java:1204)
at java.security.AccessController.doPrivileged(Native Method)
at com.dukascopy.api.impl.connect.DCClientImpl.setSubscribedInstruments(DCClientImpl.java:1204)
at com.dukascopy.api.impl.connect.DCClientImpl.connectedInit(DCClientImpl.java:701)
at com.dukascopy.api.impl.connect.DCClientImpl.authorized(DCClientImpl.java:990)
at com.dukascopy.dds4.transport.client.events.AuthorizedEvent.execute(AuthorizedEvent.java:23)
at com.dukascopy.dds4.transport.common.mina.EventTask.run(EventTask.java:35)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Again, these exceptions occur at random, I would guess 1 out of 5.
See also these bug reports, which are also related:
Bug1Bug2All together it seems that the startup process/synchronization is very unstable at the moment.
Thanks for fixing this.