Results 1 to 7 of 7

Hybrid View

  1. #1
    Hello,

    Thanks for your reply. I think it might not be related to connectivity issue, because during the first production deploy we noticed the issue was happening with a lot of clients; it is also important to say that the issue happens only on production environment and not on our test environment.
    I checked the configuration and we already have the <max_recovery_length> param set to 5000 bytes.

    Maybe some other kind of logs can help? Do you have any suggestion?

    Thanks,

    Regards

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,091
    Assuming that your setting of <max_recovery_length> was left as the default, we suggested to increase it to 5000.
    Since it was already 5000, then try 15000.
    The aim is to see if the recovery capabilities of Lightstreamer can be increased, so that when you currently see "Insufficient data for recovery" you can see a successful recovery.
    This is related to what you wrote: "recently after i increased the size of the message sent by the adapter". If the messages in transit are now big, the amount of data that should be kept to ensure recovery should be determined accordingly.
    The hope is then that successful recovery from temporary outages can change the client experience significantly.

    About the cause of the communication outages, for now there is no evidence that it can be caused by a Lightstreamer malfunctioning.
    The Server log sent is very short (300 ms of activity), yet it shows normal activity on various sessions.
    So, the interruption on a single session seems a client connectivity issue.
    Only if you notice that many clients experience problems at the same time can we suspect a Server or local network problem.

    For a preliminary check, you can send us a log of the Internal Monitor.
    Please set the LightstreamerMonitorText logger at TRACE level in lightstreamer_log_conf.xml and send us the log produced in a few hours. But please, for now, take care of extracting only the log produced by this logger, otherwise the log could be very long.
    With the current settings, you should grep for the "streamerMonitorText" pattern.

 

 

Similar Threads

  1. Replies: 25
    Last Post: September 28th, 2016, 10:33 AM
  2. SYNC Error on bind_session
    By shifter1 in forum Client SDKs
    Replies: 1
    Last Post: November 18th, 2013, 09:14 AM
  3. Upgraded to LS 4 and many POST bind_session.txt
    By Adrian Parker in forum Client SDKs
    Replies: 2
    Last Post: November 21st, 2011, 03:03 PM
  4. Replies: 0
    Last Post: November 14th, 2008, 04:53 PM

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 11:24 PM.