Hi New Soft,
This happens because the client does not receive any data from the server (not even the probe messages) for a period of time too long.
Sure, you may try to increase the timeout parameters, but I'm not sure this is the best way to solve the problem. Is therefore necessary to understand the causes of this break in the comunication between the server and the client. In general, the most common causes for such behavior are two:
- network disruptions
- a momentary pause of the server activities, for example due to a gc major collection
In any case, the behavior observed should be unrelated with subscribtion mode or other application aspects.
By analyzing the server logs in an interval of time around the time of an issue occurence you should be able to understand what is actually your scenario and therefore hypothesize possible solutions.
For example if you find that your is a GC puuses problem a possible solution is to configure the launch script of the Lightstreamer server in order to impose GC pauses shorter.
Regards,
Giuseppe
