Results 1 to 4 of 4
  1. #1
    Member
    Join Date
    Nov 2008
    Location
    Boston
    Posts
    24

    status change when the content length is reached

    Hi,

    I'm using the Moderato free edition. The lightstreamer_conf.xml contains <content_length><default>300000</default></content_length>.

    When the streaming data from the persistent connection reaches 300K, it re-starts a new connection. This is fine as it is the expected behavior.

    In normal situation, there is no status change when the content length is reached. But under certain condition, which I don't know how to reproduce, my Javascript statusChange callback function is also invoked with a new status "STREAMING" when the 300K content length limit is reached. When this happens, the statusChange() callback is called every time the 300K limit is reached and a new connection is established.

    Can someone please explain why the statusChange callback is invoked in this situation?

    Thanks,
    Richard

  2. #2
    Power Member
    Join Date
    Jul 2006
    Location
    Cesano Maderno, Italy
    Posts
    784
    hello riwang,

    that's strange and should not happen unless between the two STREAMING statuses there is something else (e.g. STALLED).
    can you check if this is the case?

  3. #3
    Member
    Join Date
    Nov 2008
    Location
    Boston
    Posts
    24
    Hi Mone,

    Since this is happening on my production server, it's hard to verify because the Javascript is minimized so it is not debuggable in Firebug. When this happens, as one user was experiencing this problem, another user saw no issue at the same time.

    But let's assume there is a STALLED status change before the STREAMING status change, what could have caused this issue?

    Thanks,
    Richard

  4. #4
    Administrator
    Join Date
    Jul 2006
    Location
    Milan, Italy
    Posts
    517
    Hi Richard,

    As I mentioned in this post, the reconnection caused by a content-length exhaustion is totally transparent to both the application and the user, and no status change at all happens.

    If you observed a status change, this was just a coincidence, probably caused a network problem or by the client CPU saturation. The transition to STALLED state cannot be related to the content-length.

    Do you have the detailed server-side logs showing the life-cycle of the user session that experimented the issue?

 

 

Similar Threads

  1. How to configure snapshot length?
    By LS_Developer in forum General
    Replies: 3
    Last Post: March 14th, 2012, 02:46 PM
  2. Will session id change when connection mode change?
    By LS_Developer in forum Client APIs
    Replies: 3
    Last Post: March 6th, 2012, 08:58 AM
  3. Connection status, CONNECTING, doesn't change
    By mr_gray in forum Client APIs
    Replies: 5
    Last Post: December 20th, 2010, 01:37 PM
  4. Initial snapshot length
    By patilgkk in forum General
    Replies: 5
    Last Post: August 2nd, 2010, 09:04 AM
  5. Dynamic Content
    By venkihere in forum Client APIs
    Replies: 7
    Last Post: October 12th, 2007, 01:14 PM

Bookmarks

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 01:52 AM.