[
https://issues.jboss.org/browse/RFPL-2345?page=com.atlassian.jira.plugin....
]
Juraj Húska commented on RFPL-2345:
-----------------------------------
I have finised testing with JBoss and his native connector. The *results are the same* as
with native connector support switched off.
I have enabled native connector as it is described
[
here|http://stackoverflow.com/a/10228684].
APR connector was started correctly, because of this log:
{code}
12:10:50,017 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-8)
Starting Coyote HTTP/1.1 on http-localhost.localdomain-127.0.0.1-8080
{code}
The usage of workarounds in the web.xml can be found
[
here|https://github.com/jhuska/showcase/blob/RF-12219/src/main/webapp-jba...].
Push: Test that messages do not become stale in a queue
-------------------------------------------------------
Key: RFPL-2345
URL:
https://issues.jboss.org/browse/RFPL-2345
Project: RichFaces Planning
Issue Type: Task
Security Level: Public(Everyone can see)
Components: testing
Affects Versions: 4.2.1.Final
Reporter: Lukáš Fryč
Assignee: Juraj Húska
Priority: Critical
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