.NET Client throwing "Session not found" error

[giuseppe.corti]

Hi vpurohit,

I confirm that you should use version 2.1.1 build 1013.

Regards,
Giuseppe

[gchermennov]

I still see this exact error when using version 2.1.6080.19963 of the client SDK. Can you advise me on how to turn on client logging?

[giuseppe.corti]

Hi gchermennov,

You can leverage the the Log4NET library (that must be included in the project - log4net.dll) and a proper configuration.
You can take this example (https://github.com/Lightstreamer/Lig...-client-dotnet) as a reference and in particular:

- the configuration file of the app https://github.com/Lightstreamer/Lig...ent.exe.config
where you can raise the log level for the categories that interest you.
- The code that adds a logger provider to the Lightstreamer client library: https://github.com/Lightstreamer/Lig...tClient.cs#L74

Regards,
Giuseppe

[gchermennov]

I can't find Log4NetLoggerProviderWrapper class in client dll

[gchermennov]

Found the class

[gchermennov]

Ok, here's what I've found after enabling client logs:

2017-01-20 23:55:44,421 [Lightstreamer listening thread] ERROR com.lightstreamer.ls_client.session - Error while listening for data in session xyz
2017-01-20 23:55:44,428 [Lightstreamer listening thread] INFO com.lightstreamer.ls_client.session - Terminating session xyz

These were logs generated by the Lightstreamer client library. Here's what my code says at the same time:

[Stream-sense queue] ERROR ProjectName.Listeners.StreamerListener - lightstreamer::communication::failure - communication failed Lightstreamer.DotNet.Client.PushConnException: Unable to read data from the transport connection: The connection was closed. ---> System.IO.IOException: Unable to read data from the transport connection: The connection was closed.

How can I investigate this further?

[giuseppe.corti]

Hi gchermennov,

The error messages reported indicate a disconnection of the communication with the server detected by the client library.
The most common cause for this type of error is a network problem, maybe a temporary network failure, could this be your case?
Otherwise you should make sure that is not the server, for some reason, deliberately terminating the connection, but in this case you need to analyze the Lightstreamer server logs.

Regards,
Giuseppe

[gchermennov]

Lightstreamer server is not under my control - I just use it to receive data updates.
Network problem can indeed be my case, I'll add code for reconnecting and continue to monitor the situation. Thanks