-
February 8th, 2012, 09:25 PM
#1
Internal cause codes
Can you give some information on what these 2 internal cause codes indicate?
internal cause code: 45
internal cause code: 39
We get a lot of these in our server logs.
-
February 9th, 2012, 09:57 AM
#2
A general consideration first.
In the log we notify at INFO level the closing of all sessions, so this is as normal as session opening.
Hence, consider that these messages may not signal any problem, if the closing occurs at the proper time.
This is why we just report internal cause codes; anyway, starting with the next release, we will report actual cause names.
Turning to your case:
We use 39 for a session that closes because it was waiting for a rebind from the client but the timeout configured with <session_timeout_mills> eventually expired.
We use 45 for a session that has been abandoned by the client, which in fact has asked for a new session and has indicated the former as an "old session" in its request.
Both cases may signal a problem in client-server communication.
The most normal close code is 38, which means that the client has interrupted its connection.
-
February 9th, 2012, 02:28 PM
#3
Can you describe exactly what 'abandoned' means? Generally what would cause a client to request a new session, passing in an old session in the request?
Thanks.
-
February 10th, 2012, 10:33 AM
#4
Hi,
it can happen for several reasons, usually it's because of a problem with the streaming socket or a timeout on a reconnection.
HTH
Similar Threads
-
By minhphan200677 in forum Adapter SDKs
Replies: 18
Last Post: November 17th, 2014, 11:10 AM
-
By jonasby1 in forum General
Replies: 4
Last Post: February 16th, 2012, 09:47 AM
-
By lisicnu in forum Adapter SDKs
Replies: 2
Last Post: December 22nd, 2011, 03:28 AM
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 02:11 AM.
Bookmarks