WSS appears to no longer terminate sessions upon query completion. The Tomcat manager can detect Session IDs (attached) for processes that have long been finished, but continue to idly persist - this behavior is fundamentally different from pre-2.0 versions of WSS. Without WSS handling the termination of sessions/processes, it is left to the Tomcat container to kill the session, which occurs after 30 minutes of inactivity.
#3 Updated by Yazan Suleiman about 4 years ago
I believe part of the problem is in RequestInfo line 120:
String contextPath = req.getSession().getServletContext().getContextPath();
This should be:
String contextPath = req.getServletContext().getContextPath();
getSession() will create a session no matter what config parameters are set
#4 Updated by Mike Stults about 4 years ago
- Resolution set to Fixed
- Target version set to 2.2.2
A code change is made in WSS 2.2.2 as Yazan recommends, the code is changed to
String contextPath = req.getContextPath();
This prevents the creation of a session per request, WSS does not use sessions as there is not state maintained for clients, so there is no need to create a session.