https://issues.apache.org/bugzilla/show_bug.cgi?id=51835
Bug #: 51835
Summary: Sessions never closes
Product: Tomcat 6
Version: 6.0.29
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: major
Priority: P2
Component: Catalina
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
Hello everyone,
We are facing non-closed sessions in our application, leading to heapspace
reach.
On our live environment, we have more than 300 sessions opened at the
same time. We have added logs telling us when a session is destroyed by
Tomcat for any cases.
We can see some correctly ended sessions with this session destroy.
We also see sessions which ended in timeout due inactivity with this session
destroy.
But we have sessions where we see neither timeout, nor session destroy in logs.
How come Tomcat could possibly never kill those sessions?
Attribution:
Version Tomcat 6.0.29
Component session listener
Environment details:
Platform and OS SunOS 5.10 Generic_142901-11 i86pc i386 i86pc
Java version 1.6.0_25-b06
Web Server Apache/2.2.16 + mod_jk/1.2.26
Footnotes:
[1] we have set this in our webapp's web.
<web-app>
[...]
<session-config>
<session-timeout>2</session-timeout>
</session-config>
</web-app>
Thank you in advance,
Best regards,
--
Voxmobili
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
