[richfaces-issues] [JBoss JIRA] (RF-12219) Push: Test that messages do not become stale in a queue

[ https://issues.jboss.org/browse/RF-12219?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12219 at 7/26/12 4:02 AM: ---------------------------------------------------------- It seems the disconnection of client doesn't destroy the session. Atmosphere calls {{$_atmosphere.unsubscribe()}} on a client on {{window.unload}} event. However the listeners on server-side aren't notified that the client is unsubscribed (might be bug in Atmosphere). I assume {{onDisconnect}} event listener of {{RequestImpl}} should be invoked in this case. However {{onResume}} event listener is invoked instead. That's why when intensively changing pages, new sessions are created and destroyed after 5 minutes. For now, I will incorporate {{org.richfaces.push.session.maxInactiveInterval}} option to allow configure this interval (see RF-12370). was (Author: lfryc): It seems the disconnection of client doesn't destroy the session. Atmosphere calls {{$_atmosphere.unsubscribe()}} on a client on {{window.unload}} event. However the listeners on server-side aren't notified that the client is unsubscribed (might be bug in Atmosphere). I assume {{onDisconnect}} event listener of {{RequestImpl}} should be invoked in this case. That's why when intensively changing pages, new sessions are created and destroyed after 5 minutes. For now, I will incorporate {{org.richfaces.push.session.maxInactiveInterval}} option to allow configure this interval (see RF-12370). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira