[
https://issues.jboss.org/browse/RF-12219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696029#comment-12696029
]
Juraj Huska edited comment on RF-12219 at 5/25/12 11:22 AM:
------------------------------------------------------------
So far I have done these steps:
1. altered richfaces showcase example, to have three pushes bound on one topic
- can be cloned from branch RF-12219 of this project
[here|https://github.com/jhuska/showcase/tree/RF-12219]
2. altered showcase functional tests for push, to open the three push examples
in an infinite loop.
The whole altered showcase tests repository can be found on branch RF-12219 of
[this|https://github.com/jhuska/qa/tree/RF-12219] project
The particular test which does this functionality
[here|https://github.com/jhuska/qa/blob/RF-12219/showcase-ftest/src/test/java/org/richfaces/tests/showcase/push/TestPushTopicsContext.java#L55-64]
To execute that particular test, please follow instructions from
[readme|https://github.com/jhuska/qa/tree/master/showcase-ftest].
Just pass {{-Dtest=TestPushTopicsContext}} as a name of the test.
3. via jvisualvm during the test executing verified:
- The number of MessageData objects is correctly handled by GC when there is
only one push on the topic.
- When there are more, and the test is executed, the number of MessageData
objects rises up to 53,000.
- This amount is not increased any more, the same applies for heap space.
- This amount depends on the number of push clients bound on the same topic
very slightly, when there were 2 pushes, then the peak of objects was 52,000,
when I increased number of pushes to three, the total amount of MessageData
increased by 1000
- When just receiving push data to these three examples, the number of
MessageData is around 0. It is increased when I am clicking between the samples
(this is what the test is trying to do).
was (Author: jhuska):
So far I have done these steps:
1. altered richfaces showcase example, to have three pushes bound on one topic
- can be cloned from branch RF-12219 of this project
[here|https://github.com/jhuska/showcase/tree/RF-12219]
2. altered showcase functional tests for push, to open the three push examples
in an infinite loop.
The whole altered showcase tests repository can be found on branch RF-12219 of
[this|https://github.com/jhuska/qa/tree/RF-12219] project
The particular test which does this functionality
[here|https://github.com/jhuska/qa/blob/RF-12219/showcase-ftest/src/test/java/org/richfaces/tests/showcase/push/TestPushTopicsContext.java#L55-64]
To execute that particular test, please follow instructions from
[readme|https://github.com/jhuska/qa/tree/master/showcase-ftest].
Just pass {{-Dtest=TestPushTopicsContext}} as a name of the test.
3. via jvisualvm during the test executing verified:
- The number of MessageData objects is correctly handled by GC when there is
only one push on the topic.
- When there are more, and the test is executed, the number of MessageData
objects rises up to 53,000.
- This amount is not increased any more.
- This amount depends on the number of push clients bound on the same topic
very slightly, when there were 2 pushes, then the peak of objects was 52,000,
when I increased number of pushes to three, the total amount of MessageData
increased by 1000
- When just receiving push data to these three examples, the number of
MessageData is around 0. It is increased when I am clicking between the samples
(this is what the test is trying to do).
> 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 Huska
> Priority: Critical
> Fix For: 4.3.0.Milestone1
>
>
> 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
