Hundreds of connections from single user

[DarioCrivelli]

Unfortunately, we have never noticed a similar pattern.

1) The first session has a normal life until the content length expires. Then, the rebind seems to be unsuccessful: the answer might be either delayed or blocked.
Could you see any "sync error" around 8:33:40/44?
Did you report the original log (which means that only activity from this client happened between 7:48 and 8:35) or did you filter the log by IP?

2) After the first failed rebind, it seems that all subsequent streaming connection attempts fail.
As a consequence, no subscription requests are issued for the new sessions, hence no data can reach the client in this phase.
You say that the clients reported no issue, but do you have any evidence that the clients also get data?
Again, did you report the original log or could there be other messages in the middle?
By the way, do you configure any specific timeout on your LightstreamerEngine.Policy instance?

[colmfield]

The first session has a normal life until the content length expires. Then, the rebind seems to be unsuccessful: the answer might be either delayed or blocked.
Could you see any "sync error" around 8:33:40/44?
Did you report the original log (which means that only activity from this client happened between 7:48 and 8:35) or did you filter the log by IP?

I didn't report the full log, but there are no sync errors around those times. There are hundreds of lines between 07:48 and 08:33, so I won't include them here unless you want them. There are sync errors for other users in that time, and immediately before the 08:33:40,536 there is an "SSL read error", but I understand these shouldn't be logged as errors at all.

2) After the first failed rebind, it seems that all subsequent streaming connection attempts fail.
As a consequence, no subscription requests are issued for the new sessions, hence no data can reach the client in this phase.
You say that the clients reported no issue, but do you have any evidence that the clients also get data?[/QUOTE]

It happens to ca.10 users, some of whom are based in my office, and I've looked at their PCs whilst it is happening and can see the data coming through ok. I haven't obviously checked with all users but am confident they would complain if it wasn't working for them - especially considering the fact they're logged on for such a long period,

By the way, do you configure any specific timeout on your LightstreamerEngine.Policy instance?

Nope, just using the default timeout here.

[DarioCrivelli]

There must be some key information missing.
Session Sfabc90480438aab8T4819101 is the only one for which subscriptions are requested and it is supposed to terminate at 8:33:44:021, when it is declared as "old" upon opening of session S79e0ab93c467ea19T3344271.
After that time, no data can flow to the client.

Fortunately, you can manage to replicate the issue.
Would it be possible for you to use a slightly modified version of your client page only on one client host in your office (in which the issue can be reproduced)?
This would allow you to collect client side log (we would give you instructions).

Are you using a single Server instance or a cluster?

Just in case any interesting log message were hidden in hundred lines, may you please send us the full log between 8:33:40 and 8:34:20?
You could send it to support@lightstreamer.com