Details
Improvement
Major
Description
A blocking connection timeout mechanism should be added to the Push Server, just like the Core, in order to release potential hanging connections in a more timely fashion. A possible scenario is when a browser crashes or gets killed a dispose-views is not send and the Push Server will not send any pongs as pings aren't being received anymore by the Core. If there are no Server Push updates, the pending blocking request will sit there until Session timeout occurs.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Just like the Core, the Push Server now has the Blocking Connection Timeout feature as well. It defaults to 90 seconds, but is configurable in the same way by setting the com.icesoft.faces.blockingConnectionTimeout (value is in milliseconds). When a blocking request is parked, a task is scheduled to be executed after the timeout occurs. This task will respond to the blocking connection with a Noop. If a response is send back before the timeout should occur, the task is canceled. Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - Just like the Core, the Push Server now has the Blocking Connection Timeout feature as well. It defaults to 90 seconds, but is configurable in the same way by setting the com.icesoft.faces.blockingConnectionTimeout (value is in milliseconds). When a blocking request is parked, a task is scheduled to be executed after the timeout occurs. This task will respond to the blocking connection with a Noop. If a response is send back before the timeout should occur, the task is canceled. Marking this one as FIXED.
Changed Fix Version(s) to 1.8.2