[richfaces-issues] [JBoss JIRA] (RF-12370) Push: Add configuration option for max session's inactive interval
Ján Jamrich (JIRA)
jira-events at lists.jboss.org
Tue Aug 7 16:40:06 EDT 2012
[ https://issues.jboss.org/browse/RF-12370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ján Jamrich closed RF-12370.
----------------------------
According to https://issues.jboss.org/browse/RF-12219?focusedCommentId=12696029&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12696029 and https://issues.jboss.org/browse/RF-12219?focusedCommentId=12697227&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12697227 the context-param triggers expected behavior.
> 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.Milestone1
>
>
> 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list