The new 2.45.35 version seems unstable as it logs JForex out sometimes.
We have older versions running in 2.45.28 on the same dedicated server. They do not logout. It is always the 2.45.35.
The server hosts 27 running JForex. Since a few (4) running on 2.34.35 this problem started. Before it was no problem.

This appears after JForex logged out:
z

Java console seems to give a reason:

2016-02-01 20:20:04.878 INFO  com.dukascopy.dds4.transport.client.i - Server: JForex platform responded with version: 4
2016-02-01 20:20:04.879 INFO  com.dukascopy.dds4.transport.client.b - Child session opened for [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443], sending [<ChildSocketAuthAcceptorMessage(parentSessionId=3c3cd4d7-ef92-4bee-a5ea-0e2fcbcfb270,timestamp=1454342579429)>], successful consequent attempt [1]
2016-02-01 20:20:14.748 INFO  com.dukascopy.dds4.transport.client.i - Server: JForex platform responded with version: 4
2016-02-01 20:20:14.748 INFO  com.dukascopy.dds4.transport.client.b - Child session opened for [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443], sending [<ChildSocketAuthAcceptorMessage(parentSessionId=3c3cd4d7-ef92-4bee-a5ea-0e2fcbcfb270,timestamp=1454342579429)>], successful consequent attempt [2]
2016-02-01 20:20:14.858 INFO  com.dukascopy.dds4.transport.client.e - Disconnect task in queue, reason [CONNECTION_PROBLEM], server address [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443], transport name [JForex platform]
2016-02-01 20:20:15.858 WARN  com.dukascopy.dds2.greed.connection.e - DISCONNECTED : [CONNECTION_PROBLEM]
2016-02-01 20:20:15.864 INFO  com.dukascopy.dds2.greed.connection.e - Sleeping for reconnect : 0
2016-02-01 20:20:15.864 WARN  com.dukascopy.dds2.greed.connection.e - CONNECTING attempt # 1
2016-02-01 20:20:15.867 INFO  com.dukascopy.dds2.greed.connection.e - Disconnected.
2016-02-01 20:20:17.002 INFO  com.dukascopy.dds4.transport.client.i - Server: JForex platform responded with version: 4
2016-02-01 20:20:17.003 INFO  com.dukascopy.dds4.transport.client.b - Primary connect successfull, primarySession is [MinaIoSessionWrapper [session=(SOCKET, R: d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443, L: /          :9790, S: d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443)]], address is [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443]
2016-02-01 20:20:18.812 INFO  com.dukascopy.dds2.greed.connection.d - !!!:Thread[(JForex platform) ClientConnector,6,javawsApplicationThreadGroup]
2016-02-01 20:20:18.814 INFO  com.dukascopy.dds2.greed.connection.e - API Authorized - 2016-02-01 19:20:18
2016-02-01 20:20:18.814 INFO  com.dukascopy.dds4.transport.client.b - Child socket connection could be accepted now by server [<ChildSocketAuthAcceptorMessage(parentSessionId=1ee41542-47a8-48cb-a218-375164cafd5f,timestamp=1454354484472)>], transport client [JForex platform, d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443]
2016-02-01 20:20:18.836 INFO  com.dukascopy.dds4.transport.synch.b - terminated
2016-02-01 20:20:18.837 INFO  com.dukascopy.dds2.greed.actions.dowjones.i - NewsLanguagesManager is shutdown
2016-02-01 20:20:18.837 INFO  com.dukascopy.dds4.transport.synch.b - terminated
2016-02-01 20:20:18.837 INFO  com.dukascopy.dds2.greed.actions.dowjones.j - NewsSubscribeManager is shutdown
2016-02-01 20:20:20.264 INFO  com.dukascopy.dds4.transport.client.i - Server: JForex platform responded with version: 4
2016-02-01 20:20:20.265 INFO  com.dukascopy.dds4.transport.client.b - Child session opened for [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443], sending [<ChildSocketAuthAcceptorMessage(parentSessionId=1ee41542-47a8-48cb-a218-375164cafd5f,timestamp=1454354484472)>], successful consequent attempt [1]
2016-02-01 20:20:20.508 INFO  com.dukascopy.dds2.greed.actions.dowjones.i - Loaded available news languages: [NewsLanguage [code=ar, name=Arabic, nationalName=العربية], NewsLanguage [code=de, name=German, nationalName=Deutsch], NewsLanguage [code=sk, name=Slovak, nationalName=Slovenčina], NewsLanguage [code=it, name=Italian, nationalName=Italiano], NewsLanguage [code=ru, name=Russian, nationalName=Русский], NewsLanguage [code=en, name=English, nationalName=English], NewsLanguage [code=es, name=Spanish, nationalName=Español], NewsLanguage [code=fr, name=French, nationalName=Français], NewsLanguage [code=he, name=Hebrew, nationalName=עברית], NewsLanguage [code=hu, name=Hungarian, nationalName=Magyar], NewsLanguage [code=bg, name=Bulgarian, nationalName=Български], NewsLanguage [code=uk, name=Ukrainian, nationalName=Українська], NewsLanguage [code=cs, name=Czech, nationalName=ÄŒeÅ¡tina], NewsLanguage [code=pt, name=Portuguese, nationalName=Português], NewsLanguage [code=ms, name=Malay, nationalName=Malay], NewsLanguage [code=ro, name=Romanian, nationalName=Român], NewsLanguage [code=sv, name=Swedish, nationalName=Svenska], NewsLanguage [code=pl, name=Polish, nationalName=Polski], NewsLanguage [code=th, name=Thai, nationalName=คนไทย], NewsLanguage [code=fa, name=Persian, nationalName=فارسی], NewsLanguage [code=zh, name=Chinese, nationalName=中文], NewsLanguage [code=ja, name=Japanese, nationalName=日本語]]
2016-02-01 20:20:20.508 INFO  com.dukascopy.dds2.greed.actions.dowjones.i - i created.
2016-02-01 20:20:20.510 INFO  com.dukascopy.dds2.greed.actions.dowjones.j - NewsSubscribeManager created.
2016-02-01 20:20:20.628 INFO  com.dukascopy.dds2.greed.connection.e - Connected to d-ja-gva-91-191
2016-02-01 20:20:20.630 INFO  org.slf4j.impl.Log4jLoggerAdapter - Authorized
2016-02-01 20:20:20.637 INFO  com.dukascopy.dds2.greed.actions.subscribe.FullDepthInstrumentSubscribeAction - FULL DEPTH INSTRUMENTS: [NZD/USD]
2016-02-01 20:20:21.779 INFO  com.dukascopy.dds2.greed.connection.e - Charts reloaded.
2016-02-01 20:20:32.423 INFO  com.dukascopy.dds4.transport.client.i - Server: JForex platform responded with version: 4
2016-02-01 20:20:32.423 INFO  com.dukascopy.dds4.transport.client.b - Child session opened for [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443], sending [<ChildSocketAuthAcceptorMessage(parentSessionId=1ee41542-47a8-48cb-a218-375164cafd5f,timestamp=1454354484472)>], successful consequent attempt [2]
2016-02-01 20:20:37.927 INFO  com.dukascopy.dds4.transport.client.e - Disconnect task in queue, reason [CONNECTION_PROBLEM], server address [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443], transport name [JForex platform]
2016-02-01 20:20:38.813 ERROR com.dukascopy.dds2.greed.connection.AccountInfoMessageWaitingHelper - Timeout (20000ms) of AccountInfoMessageInit. Restarting ...
2016-02-01 20:20:38.927 WARN  com.dukascopy.dds2.greed.connection.e - DISCONNECTED : [CONNECTION_PROBLEM]
2016-02-01 20:20:38.932 ERROR com.dukascopy.charts.data.datacache.au - 
java.lang.InterruptedException
   at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(Unknown Source)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor.awaitTermination(Unknown Source)
   at com.dukascopy.charts.data.datacache.au.close(L:2115)
   at com.dukascopy.dds2.greed.actions.connections.DisconnectAction.doDispose(L:318)
   at com.dukascopy.dds2.greed.actions.connections.DisconnectAction.GD(L:113)
   at com.dukascopy.dds2.greed.connection.AccountInfoMessageWaitingHelper.Mi(L:277)
   at com.dukascopy.dds2.greed.connection.AccountInfoMessageWaitingHelper.run(L:209)
   at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
   at java.util.concurrent.FutureTask.run(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
2016-02-01 20:20:39.127 INFO  com.dukascopy.dds4.transport.client.e - Disconnect task in queue, reason [CLIENT_APP_REQUEST], server address [d-ja-gva-91-191.dukascopy.com/194.8.15.191:10443], transport name [JForex platform]

Please fix.

It keeps on happening. My assumption: It could be if the Internet connection gets interrupted for a short time while JForex is checking the account.
Please fix this. Older versions did not logout as they were more tolerant in this manner.

It must be fixed soon, as it destroys any track record. A logged out JForex does not trade.

It keeps on happening on 2.45.37 as well.
I am on holiday and I have to work with a worse Internet connection. JForex logs out from time to time.

Please fix this urgently, as this happens on the server as well if the connection is interrupted in the wrong moment.

Hi support team,

any process on this topic?
Thank you for an update!

I'm almost sure that this is due to very slow connection.

We ignored the fact that some messages were not received before. We throw out of the platform in case of not receiving one of the most important messages for 20 seconds now. It heavily reduces the load on our servers as the connection will most probably be unstable anyway and lead to many timeouts and messages lost.
In all the case I've investigated so far, this message was sent by server, but was not received on platform within 20 seconds. Transport confirmed a timeout of 10 seconds after which the disconnect was initiated. Please provide your login and the date of the problem. I will check that as well.

We would like to continue with reacting on slow internet connections by throwing out of the platform. However, besides not received message within 20 seconds, we will ping the server with 50Kb of data. If the result will be very slow, we will throw out. If not, we will initiate reconnect.

Hi,

this cannot be a solution on your side!
These logouts also happened on our Dedicated Server
with Intel Quadcore 4 x 3.7 GHz i5-4590, 32 GB of RAM
located at DATADOC in Strasbourg https://www.datadock.eu/en/datadock.php
They have a very strong backbone and the Dedicated Server is connected to a 1000 Mbit/s Internet line. The ping latency is 15 ms average to the DC trading server only.

If you log out the platform you endanger our trading!
On live and on demo! This destroys any track record!
Just consider if you log out the platform on the Dedicated Server side, just because of any connection problem reason?
It could be even caused on your server side as well. There is always some maintenance somewhere, which could cause a small interruption whatsoever.
Logging out cannot be the right way of optimizing your servers!

You cannot throw your customers out automatically, just because there are a few short Internet disconnections in a while!

Please fix this, otherwise we cannot trust the platform.

Please provide the login and the day when this happened on your dedicated server. We will investigate it.

It is more stable at the moment, no log outs for about a week. I will send you an email if this happens again.
Generally it is the wrong way to log out customers from the trading platform, even if it is demo, just because of lag in the Internet connection.
Well working demo trading builds up trust.

Version 2.45.39 is out on DEMO and LIVE. It should not throw out in case of not received messages anymore. Please bare in mind, that in case this AccountInfoMessage is not received, the information regarding the positions, oders and your funds might be incorrect.