[
https://issues.jboss.org/browse/RF-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708000#comment-12708000
]
Lukáš Fryč edited comment on RF-12219 at 7/26/12 4:05 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 experimental option
{{org.richfaces.push.session.maxInactiveInterval}} 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.
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).
> Push: Test that messages do not become stale in a queue
> -------------------------------------------------------
>
> Key: RF-12219
> URL: https://issues.jboss.org/browse/RF-12219
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.2.1.Final
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 4.3.0.Milestone2
>
>
> According to the [Forum reference],
> we can have problems with stale messages.
> I would suggest to write tests for following scenarios and check that queue
> is destroyed properly:
> * view expires
> * client leaves the page with {{a4j:push}} without proper clean up
> * ...
> Let's brainstorm other scenarios.
--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
