Results 1 to 10 of 10

Hybrid View

  1. #1
    Member
    Join Date
    Dec 2008
    Location
    Bangalore
    Posts
    20

    Question Request Refused and sync error

    Hi,

    I am getting the below message some times. It just starts and never seem to end when ever it starts.

    Code:
    <WARN> received a request too long in the body part: request refused
    Also, I keep getting(Not related to above problem):

    Code:
    25.Mar.09 18:51:57,612 < INFO> Sync error: Can't find session from ipaddress:portnumber
    25.Mar.09 18:51:57,612 < INFO> Controlling session: S8ea5728e451e9043T5110657 from ipaddress:portnumber
    Can you please tell what could be going wrong and where? Can this be a network issue?

    Thanks,
    Shreyas

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,090
    The "request too long" check is driven by the <request_limit> Server configuration element.
    The various client libraries try to avoid to send requests too long. They can't avoid it only in case of unusually long group/schema names, user names or user messages.
    If you feel that this is not your case, please provide us with more details.

    The "Sync error" can be due to delayed client requests, which refer to seesions that have already expired. This may depend on client machine overload or on network issues. By increasing the <session_timeout_millis> Server configuration setting you can allow for longer delays.

  3. #3
    Member
    Join Date
    Dec 2008
    Location
    Bangalore
    Posts
    20
    Hi Dario,

    I think the first error is happening because of "unusually long group/schema names, user names or user messages". I increased the <request_limit> tag to 500000. It seems to be working fine currently. Thanks, will update you if I find any thing again.

    I also increased the <session_timeout_millis> to 50000 and <max_polling_millis> to 150000. It was 5000 and 15000 initially.

    I had this exception in the log. I hope this is not anything serious or non-recoverable issue.

    Code:
    Failure in HTTP connection on Lightstreamer HTTP Server
    com.lightstreamer.b.l
    	at com.lightstreamer.d.b.a.b(a.java)
    	at com.lightstreamer.d.b.a.a(a.java)
    	at com.lightstreamer.d.b.bb.d(bb.java)
    	at com.lightstreamer.b.h.h(h.java)
    	at com.lightstreamer.a.d.g(d.java)
    	at com.lightstreamer.b.bb.a(bb.java)
    	at com.lightstreamer.b.bb.a(bb.java)
    	at com.lightstreamer.b.e.b(e.java)
    	at com.lightstreamer.f.a.x.b(x.java)
    	at com.lightstreamer.f.a.i.a(i.java)
    	at com.lightstreamer.f.a.l.a(l.java)
    	at com.lightstreamer.f.a.l.a(l.java)
    	at com.lightstreamer.f.a.l.a(l.java)
    	at com.lightstreamer.b.nb.a(nb.java)
    	at com.lightstreamer.b.f.h(f.java)
    	at com.lightstreamer.a.d.g(d.java)
    	at com.lightstreamer.b.bb.a(bb.java)
    	at com.lightstreamer.b.lb.a(lb.java)
    	at com.lightstreamer.b.lb.b(lb.java)
    	at com.lightstreamer.b.fb.a(fb.java)
    	at com.lightstreamer.j.y.a(y.java)
    	at com.lightstreamer.j.f.a(f.java)
    	at com.lightstreamer.j.c.b(c.java)
    	at com.lightstreamer.j.c.a(c.java)
    	at com.lightstreamer.f.p.b(p.java)
    	at com.lightstreamer.f.p.a(p.java)
    	at com.lightstreamer.f.cb.a(cb.java)
    	at com.lightstreamer.a.nc.run(nc.java)
    	at com.lightstreamer.a.ad.a(ad.java)
    	at com.lightstreamer.a.bd.run(bd.java)
    Thanks,
    Shreyas

  4. #4
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,090
    May you specify the Server build number, please?

  5. #5
    Member
    Join Date
    Dec 2008
    Location
    Bangalore
    Posts
    20
    Lightstreamer Server version 3.5 build 1422

  6. #6
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,090
    The issue is not serious and it shouldn't be signaled by a stack trace. We will fix that.
    It is caused by a rare race condition, in which a session is closed while it is being recalled by a rebind request. It is a special case of the condition that leads to the "Sync error".
    The only problem is that the client, upon the closing of the session, may not be able to recover by opening a new session automatically.

 

 

Similar Threads

  1. Sync Errors
    By wwatts in forum Client SDKs
    Replies: 1
    Last Post: February 20th, 2012, 10:14 AM
  2. Sync Errors
    By colmfield in forum Client SDKs
    Replies: 2
    Last Post: September 22nd, 2010, 10:06 AM
  3. Sync errors in server log
    By riwang in forum Client SDKs
    Replies: 29
    Last Post: June 28th, 2010, 12:56 PM
  4. StockListDemo (sync on different windows)
    By CitiMan in forum General
    Replies: 4
    Last Post: November 21st, 2006, 12: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 02:01 PM.