disconnection problems

magnum_rg

Hi,

We made a simple chat application based on LS demo, everything works fine, but there is one problem: when user connects through intranet (office proxy, firewall), it gets random disconnections, between 30 sec~5 min, and to stay alive on the system a user must send a message to room periodically (any browser). An application works fine even when a user connects through a public anonymous proxies.

We found this log entries on lost connections:

10-Aug-11 00:18:46,915|INFO |LightstreamerLogger.requests |FOR PUMPS PARKING DESTROYER|Closed session Sdbb678172695551cT1556670 with internal cause code: 39
.....

Mone

Hi,

a bigger log is necessary to try and understand what's happening.
If possible send a log containing a complete session from when the application is open until it is unexpectedly disconnected.

Sorry, did I understand correctly that intranet users have problems while internet users don't?

magnum_rg

Yes, an intranet user usually connects through a firewall, like Microsoft ISA Server, etc. (from office or public networks). I think it is a 'keep-alive' related issue, because if user sends a messages to rooms every 5-10 sec., no disconnections happens.

Please check an attachment, there is only one user in chat room, connection time is '07:45:26', disconnection on '07:46:36,430'

Mone

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

magnum_rg

00:19:46,026

Mone

Hi

looks like the client in your log switched to polling @ 00:16:25,168
This is the request that instructs the server to transform the streaming session in a long-polling one:

/lightstreamer/control.js --> LS_session=Sf0d3e570bb765902T1620696&LS_op=force_rebind&LS_cause=sense&LS_unique=2&

the last poll for this session is @ 00:19:36,019. The connection of the last poll is reused @ 00:19:36,020 but then the server didn't receive the "next" request.

So looks like you have two problems with these clients:
first your client cannot stream; probably one of the mentioned firewall/proxy is caching the entire response before forwarding it to the actual client

the second issue is with the request from the client not reaching the server anymore; to verify what happens here you should analyze the traffic both client side and server side; if you see the request exit the client but not reaching the server than something in the middle is even "eating" requests

let me know what you find out.

As thing turned out it may be good also to set the LightstreamerLogger.connections.http category to DEBUG.

HTH