Results 1 to 2 of 2
  1. #1
    Senior Member
    Join Date
    Dec 2019

    Closed session due to internal cause on server side


    Why the client receives such a message from the server?

    "Closed session ###### with internal cause code: 32 (Close forced on the server side)"

    and sometimes code : 31

  2. #2
    Join Date
    Jul 2006
    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

  1. Replies: 15
    Last Post: April 29th, 2022, 10:04 PM
  2. Replies: 1
    Last Post: June 13th, 2016, 10:01 AM
  3. Replies: 5
    Last Post: January 18th, 2016, 10:10 AM
  4. Internal cause codes & Session callbacks
    By jonasby1 in forum General
    Replies: 4
    Last Post: February 16th, 2012, 08:47 AM
  5. Internal cause codes
    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
All times are GMT +1. The time now is 12:19 AM.