-
January 21st, 2010, 09:16 AM
#2
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 notifyNewSession returns 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.
Similar Threads
-
By vaduganathan in forum Client SDKs
Replies: 3
Last Post: April 9th, 2010, 08:58 AM
-
By jweber in forum Client SDKs
Replies: 10
Last Post: February 10th, 2010, 09:25 AM
-
By CitiMan in forum Adapter SDKs
Replies: 8
Last Post: November 30th, 2006, 04:26 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 12:34 AM.
Bookmarks