Quote Originally Posted by DarioCrivelli
First of all, in the attached file you mention a value of 10 ms for <session_timeout_millis>, but I assume you mean 10 seconds.
Yes it is 10 seconds. not 10 ms.

Quote Originally Posted by DarioCrivelli
Indeed, your client seems to be receiving a lot of data to be elaborated, about 300KB in 15 seconds at least.
This may cause the browser to be overwhelmed. May you please confirm that by direct observation of the client machine?

This would explain the "Sync error", as the page would issue the request of rebinding to the session long time after the previous connection has closed.
Server is sending approximately 80 KB in first control request

and After adding tables to page, it is expected upto 170 KB of data to be pushed in second request.

In such case, If we use default 5 seconds session_timeout_millis and 300 KB of content-length will be ok?

Quote Originally Posted by DarioCrivelli
Note that you might increase the <session_timeout_millis> and the content-length, but that would just postpone the problem. In fact, in the third case (with the increased content-length), before the whole content-length has been consumed, the client opens a new session in polling mode. This is a recovery mechanism adopted by Lightstreamer web client library when it detects that the update processing is slower than the incoming update rate.
Because as you said, increasing session_timeout_millis and the content-length just postpones the issue.

Please giude me to handle this situation.