Hi Kevin,

That's a known bug that was fixed in the latest version.
The bug affects the 6.1.4 and 6.2.2 versions.

The bug is triggered by the client being unable to reach the server
http://www.lightstreamer.com/distros...TML#web_client

We considered the bug while investigating the issue, but it does not seem likely it to be related to your issue, as the browser would not permit so many open sockets to the server in the first place (the number of open sockets is way too high with respect of the active sessions).

Anyhow, you can monitor the impact of the issue on the server by monitoring the log for lines like the following:

xxxxxxxx |INFO |LightstreamerLogger.webServer |SERVER POOLED THREAD 2 |Serving request: /lightstreamer/xhr.html?id=3&domain=lightstreamer.com& on "Lightstreamer HTTP Server" from xxxxxxx

My colleagues will get back to you about the issue in general ASAP