Results 1 to 2 of 2

Thread: Sync Errors

  1. #1
    Join Date
    Oct 2007
    Colorado Springs

    Sync Errors

    We have a client that initializes a number of subscriptions to different items. Sometimes during this process, we receive and error on the client that states "The underlying connection was closed. The connection was closed unexpectedly". Reviewing the Lightstreamer log file we see the following error code 38 being reported with a Sync Error.

    17-Feb-12 14:12:18,261|INFO |LightstreamerLogger.requests |FOR PUMPS PARKING DESTROYER|Closed session Sfde77fce01081e71T0851448 with internal cause code: 38
    17-Feb-12 14:12:20,383|INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 9 |Serving request: /lightstreamer/control.txt --> LS_session=Sfde77fce01081e71T0851448&LS_op=destroy from
    17-Feb-12 14:12:20,383|INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 9 |Destroying session: Sfde77fce01081e71T0851448 from
    17-Feb-12 14:12:20,383|INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 9 |Sync error: Can't find session from

    Note that the IP addresses have been removed for sanitization reasons. Could you please help us understand what might be happening and possibly what internal cause code 38 might be? For your information we are using Presto 4.0.1 version of Lightstreamer running on a windows 2008 R2 server and the client is currently running on windows XP using a C# implementation for both the client and Data Adapters.

    Thanks in advance for the help.

  2. #2
    Join Date
    Jul 2006
    From the Server perspective, the connection was closed by the Client (this is the error 38).
    However, as suggested by the exception you received, from the Client perspective, the connection was closed by the Server.
    We should clarify if the two messages refer to the same or different connections.
    Did you receive the exception upon a subscribe call or through onFailure on the connection listener?

    The subsequent "sync error" may be just a consequence:
    When the Client finds a broken connection, it still tries to inform the Server that the session is no longer needed with a "destroy" request.
    In this case, the session has been already closed, because the Server has noticed the connection break, hence the error.
    However, the "sync error" demonstrates that the client-server connectivity is still working after the issue.



Similar Threads

  1. Sync Errors
    By colmfield in forum Client SDKs
    Replies: 2
    Last Post: September 22nd, 2010, 10:06 AM
  2. Sync errors in server log
    By riwang in forum Client SDKs
    Replies: 29
    Last Post: June 28th, 2010, 12:56 PM
  3. Request Refused and sync error
    By shreyaspurohit in forum Adapter SDKs
    Replies: 9
    Last Post: March 31st, 2009, 11:11 AM
  4. StockListDemo (sync on different windows)
    By CitiMan in forum General
    Replies: 4
    Last Post: November 21st, 2006, 12:14 PM


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 09:42 AM.