-
December 2nd, 2020, 02:08 PM
#10
Unfortunately, the client error you mentioned (LS_cause=new.timeout.5 .2.error) is not enough to figure out what is going on.
Indeed, the error means that the client was unable to create the session in the expected time and therefore tries again.
This scenario can be caused both by client-side problems such as poor network conditions, and server-side problems with severe delays on the server.
You should check the server log looking for messages like this "Current delay for tasks scheduled on thread pool SERVER is ... seconds".
About missing updates, still valid my previous reply, with a log configuration good for troubleshooting this kind of issue.
Regards,
Giuseppe
Similar Threads
-
By kailashb in forum Adapter SDKs
Replies: 2
Last Post: August 20th, 2015, 11:41 AM
-
By Slavko Parezanin in forum Adapter SDKs
Replies: 1
Last Post: January 19th, 2015, 09:43 AM
-
By thanie2001 in forum Client SDKs
Replies: 5
Last Post: August 20th, 2009, 10:38 AM
-
By Mone in forum Client SDKs
Replies: 2
Last Post: October 17th, 2008, 09:22 AM
-
By Mone in forum Client SDKs
Replies: 1
Last Post: April 19th, 2007, 07:42 PM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 03:02 PM.
Bookmarks