-
August 28th, 2023, 08:26 AM
#1
There are several cases of close forced on the server side.
It may be a close requested via JMX or by the Metadata Adapter or a refusal due to configured exclusion rules.
Do you see any explanation message in the Server log just before the reported message?
If not, please try setting the LightstreamerLogger.connections logger at INFO level.
Case 31 ("Destroy invoked by client") is more common.
In fact, a client can close a session at will and it is sufficient for it to close the TCP connection.
However, the client SDK libraries, when possible, also send a "destroy" request to the Server before closing, to ensure that the Server also closes the TCP connection on its side.
If the "destroy" reaches the Server, the Server logs code 31, but the case is not different from the more common 38 ("Connection interrupted by client").
Similar Threads
-
By baalbaki in forum Adapter SDKs
Replies: 15
Last Post: April 29th, 2022, 10:04 PM
-
By carenot in forum General
Replies: 1
Last Post: June 13th, 2016, 10:01 AM
-
By tsezuu in forum Client SDKs
Replies: 5
Last Post: January 18th, 2016, 10:10 AM
-
By jonasby1 in forum General
Replies: 4
Last Post: February 16th, 2012, 08:47 AM
-
By BKnight in forum General
Replies: 3
Last Post: February 10th, 2012, 09:33 AM
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 10:24 PM.
Bookmarks