[
https://issues.jboss.org/browse/RF-12219?page=com.atlassian.jira.plugin.s...
]
Juraj Húska commented on RF-12219:
----------------------------------
I ran my testing method as Lukas had proposed with these results. For each of the options
I ran test for 7 minutes, and I was checking again number of MessageData instances.
* org.richfaces.push.session.maxInactiveInterval configured to 40000
** number of instances: 1,536
* org.atmosphere.cpr.CometSupport.maxInactiveActivity configured to 35000
** number of instances: 93,853
** I have put this init-param to Facet Servlet, however the results are similar to the
testing without using any workaround. Like it is not working as expected.
* both workarounds used
** number of instances 1,585
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