Internal cause codes & Session callbacks

[ekrutz]

Dario, we are seeing several instances of the following in our logs:

20-Jan-12 14:07:52,695|INFO |LightstreamerLogger.requests |FOR PUMPS PARKING DESTROYER|Closed session Se6150bc443e107beT5831853 with internal cause code: 38

This is similar to the issue above. Can you clarify that this means the LS server thinks the client disconnected from it? And therefore, the LS server will stop sending updates to the client.

What are typical root causes when seeing a high number of these?

[DarioCrivelli]

I confirm that, upon the above kind of closure, the Server finds the socket closed by the client.
So, the Server can no longer send updates to the client and it can only wait for the client to connect again and open a new session.
When the client resubscribes to the same items, the lost updates can still be sent to it as part of the snapshot. The way depends on the subscription mode and other subscription settings.

If you see many 38 closures at the same time, that could be caused by an interruption at network level.
Serious problems on the Server side, leading to repeated "current delay ..." log messages could also cause that.
If you see many subsequent 38 closures for the same client, client side problems are also possible; see this thread, for instance.

[DarioCrivelli]

A post here was moved to a new thread