[
https://issues.apache.org/jira/browse/PLUTO-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Gould updated PLUTO-474:
---------------------------------
Fix Version/s: (was: 1.2.0)
1.1.5
Affects Version/s: (was: 1.2.0)
1.1.5
I cloned this because I know that this problem still exists in 1.1.x, but I'm
not sure about trunk. I'm not sure if cloning the issue was the right thing to
do, but I guess if it wasn't I bungled it up. Anyhow, this is still a problem
in 1.1.4.
> CLONE -portlet session should not be invalidated when lastAccessedTime is 0
> ---------------------------------------------------------------------------
>
> Key: PLUTO-474
> URL: https://issues.apache.org/jira/browse/PLUTO-474
> Project: Pluto
> Issue Type: Bug
> Components: portlet container
> Affects Versions: 1.1.5
> Reporter: Benjamin Gould
> Priority: Critical
> Fix For: 1.1.5
>
>
> Some servlet containers do not automatically initialized the lastAccessedTime
> for new sessions they create. They wait until the next request occurs. For
> example in jetty this servlet will print out "0" the first time you access it:
> public void doGet(HttpServletRequest request, HttpServletResponse
> response) throws ServletException, IOException {
>
> response.getWriter().println(request.getSession(true).getLastAccessedTime());
> }
> and then subsequent access print out the current time as you would expect.
> Pluto's PortletRequestImpl#getPortletSession() method does not work correctly
> for these servlet containers because it assumes that the session's
> lastAccessTime has been initialized. When that time has not been initialized
> it proceeds to invalidate the session since it thinks the session has
> exceeded the maxInactiveInterval.
> Another problem in this method is that when an httpSession has been
> invalidated it is still used by the cached portletSession.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
