Request Refused and sync error

**shreyaspurohit** · March 26th, 2009, 09:03 AM

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

**DarioCrivelli** · March 26th, 2009, 09:37 AM

May you specify the Server build number, please?

**shreyaspurohit** · March 26th, 2009, 09:42 AM

Lightstreamer Server version 3.5 build 1422

**DarioCrivelli** · March 26th, 2009, 11:56 AM

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.

**shreyaspurohit** · March 26th, 2009, 01:38 PM

"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."

So, does this mean, the client has to close and open the application again? I mean, what is the impact of this on an application. The app is basically pushing quote data to front end.

Thanks,
Shreyas

**DarioCrivelli** · March 27th, 2009, 08:59 AM

Thinking again to the race condition that can cause a session to be closed while it is being recalled by a rebind request,
there should be no case in which this can lead to an incorrect behaviour on the Web Client Library:
the closed session should always be obsolete, thus not needing to be recovered.

Please provide us with a longer Server log snippet, containing the above stack trace, so that we can ensure that this is the case.