lstest
Hi,
for our application we need to know exactly when a client disconnects from the server.
Unfortunately in some cases (about 20% of all disconnects) Lightstreamer does not seem to notice that a client is no longer connected (notifySessionClose does not get called).
Could you give us a hint, what might cause this problem?
Many thanks in advance!
Dario Crivelli
notifySessionClose is guaranteed to be eventually called for any session,
that is, the same number of times notifyNewSession returns successfully.
Compared with the corresponding client disconnection, it may just be delayed of a few seconds,
depending on the <session_timeout_millis> configuration flag.
If you can identify and replicate a case in which notifyNewSessionreturns successfully, then the client is closed, but notifySessionClose is never called,
then please show us the Server log,
taken with default log settings and the LightstreamerLogger.connections logger at INFO level.
Some intermediate proxy might keep a streaming connection alive after the connection from the browser has been broken.
lstest
Hi,
although it's a bit late, I would like to let you know that notifySessionClose WAS called.
The problem was that we registered two different tables and we received notifySessionClose from one or the other table, but not from both.
We have now fixed our problem.
Thanks for your help!
