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

[Milo van der Zee (JIRA)]

    [ https://issues.jboss.org/browse/RF-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12692582#comment-12692582 ] 

Milo van der Zee commented on RF-12219:
---------------------------------------

I created a testcase in which I push an event every two seconds. I see that a org.richfaces.application.push.MessageData object is created every two seconds for every logged on session. The objects are never killed and stay there forever. Somehow the production environment reaches a state that a couple a hundred objects are created for each push request. And because I'm using the push system in a couple of places the result is that about 2000 objects are created every minute.
Also in the test environment the number of objects never declines. The count only increases.

In my current situation in production I disabled a couple of push generators and with only one left I see 363 new MessageData objects every push moment. There are 34 session from which there are 27 active. So on average instead of one object per session I see about 11 objects per session for each push event.

Conclusions:
- cleanup system fails completely
- listener registration faulty

And it could still be that I'm using push the wrong way... Do I need to consume events?

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: 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