You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2006/06/12 02:08:31 UTC
[jira] Resolved: (PLUTO-242) Portlet session is invalidated when
maxInactiveInterval < 0
[ http://issues.apache.org/jira/browse/PLUTO-242?page=all ]
Craig Doremus resolved PLUTO-242:
---------------------------------
Resolution: Fixed
Patch added to SVN in revision 413550. Thank you David.
> Portlet session is invalidated when maxInactiveInterval < 0
> -----------------------------------------------------------
>
> Key: PLUTO-242
> URL: http://issues.apache.org/jira/browse/PLUTO-242
> Project: Pluto
> Type: Bug
> Components: portlet container
> Versions: 1.1.0-beta1
> Reporter: David Garcia
> Assignee: Craig Doremus
> Fix For: 1.1.0
> Attachments: PortletRequestImpl_patch
>
> When maxInactiveInterval is negative, portlet session should never timeout, but it does when you call portletSession.setMaxInactiveInterval(-1) (any negative number will do).
> The problem is the calculation made in org.apache.pluto.internal.impl.PortletRequestImpl:
> if (currentInactiveTime > maxInactiveTime) {
> ...
> httpSession.invalidate();
> ...
> }
> As maxInactiveTime is negative, the condition is always true.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira