[
https://issues.jboss.org/browse/RF-12370?page=com.atlassian.jira.plugin.s...
]
Cody Lerum commented on RF-12370:
---------------------------------
Dropping the following into web.xml appears to be a workaround if you can't move to
4.3.x yet (35 second timeout)
{code}
<context-param>
<param-name>org.atmosphere.cpr.CometSupport.maxInactiveActivity</param-name>
<param-value>35000</param-value>
</context-param>
{code}
Push: Add configuration option for max session's inactive
interval
------------------------------------------------------------------
Key: RF-12370
URL:
https://issues.jboss.org/browse/RF-12370
Project: RichFaces
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: core
Affects Versions: 4.2.2.Final
Reporter: Lukáš Fryč
Assignee: Lukáš Fryč
Fix For: 4.3.0.M1
When investigating RF-12219, I have found, the sessions aren't destroyed when client
disconnects properly ({{$_atmosphere.unsubscribe()}} on {{window.unload}}).
We should allow to configure maximum time before the Session gets destroyed
automatically.
{code:xml}
<context-param>
<param-name>org.richfaces.push.session.maxInactiveInterval</param-name>
<!-- interval in miliseconds; default value: 5 minutes -->
<param-value>300000</param-value>
</context-param>
{code}
Further investigations in scope of RF-12219 are needed.
--
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