Results 1 to 10 of 11

Hybrid View

  1. #1

    .NET Client throwing "Session not found" error

    When sending multiple notifications, our .NET client session not found error. Sometimes we get this error right after receiving 1st notification and sometimes after receiving 10 notifications.

    Here is what we see in client logs -

    Lightstreamer.DotNet.Client.PushServerException: Session not found
    at Lightstreamer.DotNet.Client.PushServerTranslator.C heckAnswer(LSStreamReader answer)
    at Lightstreamer.DotNet.Client.PushServerProxy.Resync Session()
    at Lightstreamer.DotNet.Client.ServerManager.Rebind(A ctivityController activityController)


    Server logs shows -

    08-Jul-16 17:56:32,819|INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 10 |Sync error: Can't find session S5d3e6790e70d1262T5446234 on "Lightstreamer HTTP Server" from 10.34.47.4:22524 []

    We are using the latest version of .NET Client SDK

    Also, we changed ConnectionInfo.ContentLength to 0, so server can set the content length but didn't make any difference.

    Any idea on what could go wrong?

  2. #2
    Administrator
    Join Date
    Feb 2012
    Location
    Milano
    Posts
    543
    Hi vpurohit,

    It seems that this is a case in which the client fails to complete successfully the operation of session rebind (at least within a certain period of time).
    However it seems strange to me that this happens also after a single notification received from the server. It was very large notification that exhaust the content length by itself, or it is a polling mode session that lives for a long time.

    Anyway, please could you isolate one or two cases of this type and send (to support@lightstreamer.com) the complete log of the client and a snippet of the server log that includes the entire life of the blamed session?

    In cases like this it is always better to keep the content length value as large as possible, so I would keep the default value or even bigger. Instead, the value chosen by the server is quite small in the factory configuration.
    Finally, please could you confirm the exact version of the client lib in use? I am asking this because in the recent version 2.1.1 build 1013 have been introduced bug fixes just concerning the rebind operation.

    Regards,
    Giuseppe

  3. #3
    Quote Originally Posted by giuseppe.corti View Post
    Hi vpurohit,

    It seems that this is a case in which the client fails to complete successfully the operation of session rebind (at least within a certain period of time).
    However it seems strange to me that this happens also after a single notification received from the server. It was very large notification that exhaust the content length by itself, or it is a polling mode session that lives for a long time.

    Anyway, please could you isolate one or two cases of this type and send (to support@lightstreamer.com) the complete log of the client and a snippet of the server log that includes the entire life of the blamed session?

    In cases like this it is always better to keep the content length value as large as possible, so I would keep the default value or even bigger. Instead, the value chosen by the server is quite small in the factory configuration.
    Finally, please could you confirm the exact version of the client lib in use? I am asking this because in the recent version 2.1.1 build 1013 have been introduced bug fixes just concerning the rebind operation.

    Regards,
    Giuseppe
    Thanks for quick update. We'll re-run the test and provide the logs soon.
    Btw - it is 2.1.1 build 1013 for us. Should we downgrade to the previous build in this case?

  4. #4
    Administrator
    Join Date
    Feb 2012
    Location
    Milano
    Posts
    543
    Hi vpurohit,

    I confirm that you should use version 2.1.1 build 1013.

    Regards,
    Giuseppe

  5. #5
    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?

  6. #6
    Administrator
    Join Date
    Feb 2012
    Location
    Milano
    Posts
    543
    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

 

 

Similar Threads

  1. Replies: 4
    Last Post: April 8th, 2015, 03:55 PM
  2. Failure to connect, "/null not found"
    By mbenson in forum Client APIs
    Replies: 2
    Last Post: March 17th, 2014, 12:59 PM
  3. Replies: 1
    Last Post: January 31st, 2011, 08:47 AM
  4. Replies: 1
    Last Post: June 7th, 2010, 12:13 PM
  5. Replies: 4
    Last Post: February 5th, 2010, 04:12 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 01:56 AM.