[JBoss JIRA] (RFPL-2807) Component reference: rich:notify, notifyMessage, notifyMessages missing styleClass description
by Jiří Štefek (JIRA)
Jiří Štefek created RFPL-2807:
---------------------------------
Summary: Component reference: rich:notify, notifyMessage, notifyMessages missing styleClass description
Key: RFPL-2807
URL: https://issues.jboss.org/browse/RFPL-2807
Project: RichFaces Planning
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: doc
Environment: RichFaces 4.3.2-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Reporter: Jiří Štefek
There are not described styleClasses in component reference:
* notify: rf-ntf-span
* notifyMessage: rf-ntf-msg
* notifyMessages: rf-ntf-msgs
They are not in any notify*.ecss.
These classes are used only for a generated empty span element of the component. So are they useless for user and should be deleted?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (RFPL-2345) Push: Test that messages do not become stale in a queue
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/RFPL-2345?page=com.atlassian.jira.plugin.... ]
Cody Lerum commented on RFPL-2345:
----------------------------------
I ran into this on 7.1.3.Final with the native and non-native connectors. What happened was that I would end up with thousands of close_wait connections on the server.
Added the following to web.xml and it appears to be cleaning up properly now.
{code}
<context-param>
<param-name>org.atmosphere.cpr.CometSupport.maxInactiveActivity</param-name>
<param-value>35000</param-value>
</context-param>
{code}
> 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č
> Priority: Critical
> Fix For: 5-Tracking
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years