[PLUTO-436] portlet session should not be invalidated when lastAccessedTime is 0

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.2.0
• Component/s: portlet container
• Assignee: Unassigned
• Reporter: Paul Franklin McMahan
• Created: 03/Oct/07 19:05
• Updated: 13/Mar/08 15:01
• Resolved: 05/Oct/07 11:16

Description

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.

Issue Links

• duplicates: PLUTO-435 PortletSession attributes aren null when using Spring instead of Generic Portlet
• is cloned by: PLUTO-474 CLONE -portlet session should not be invalidated when lastAccessedTime is 0