[
https://issues.jboss.org/browse/RF-12219?page=com.atlassian.jira.plugin.s...
]
Milo van der Zee commented on RF-12219:
---------------------------------------
Hello Lukáš,
thank you very much and nicely found in the Comet software. Looking good :)
In my situation my workaround still functions like a charm. An enhancement could be to use
the id of the push component combined with the session id (See PushResource.java near
"UUID.randomUUID()"). That would naturally limit the number of queues.
MAG,
Milo van der Zee
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: Juraj Húska
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