[
https://issues.jboss.org/browse/RF-12219?page=com.atlassian.jira.plugin.s...
]
Milo van der Zee edited comment on RF-12219 at 5/14/12 5:27 AM:
----------------------------------------------------------------
I'm checking the server with Cacti and the script I wrote does not use cookies to
re-use existing sessions. So every minute Cacti creates a session that expires after 30
minutes. Seeing that the push system creates enormous amounts of MessageData objects it
looks like the expired sessions are still sent a push event that then is never destroyed.
I'll see if I can create a test-case for this hypothesis. I'll start pushing in a
second interval and I'll open a whole bunch of sessions.
was (Author: MilovdZee):
I'm checking the server with Cacti and the script I wrote does not use cookies to
re-use existing sessions. So every minute Cacti creates a session that expires after 30
minutes. Seeing that the push system creates enormous amounts of MessageData objects it
looks like the expired sessions are still sent a push event that then is never destroyed.
I'll see if I can create a test-case for this hypothesis.
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: Enhancement
Security Level: Public(Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.1.Final
Reporter: Lukáš Fryč
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