You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2011/09/16 15:52:39 UTC

DO NOT REPLY [Bug 51835] New: Sessions never closes

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: dev@tomcat.apache.org
        ReportedBy: integration@voxmobili.com
    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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 51835] Sessions never close

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51835

Voxmobili <in...@voxmobili.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Sessions never closes       |Sessions never close

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 51835] Sessions never close

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51835

--- Comment #1 from Konstantin Kolinko <kn...@gmail.com> 2011-09-16 16:27:14 UTC ---
1. Are you sure that it is not a bug in your logging? You are not telling much
about it.
E.g. maybe you are not taking into account that session id changes during
authentication (since 6.0.21).

2. Note also, that expired sessions are not evicted immediately upon expiring,
but only when background processing thread finds them.  See
"backgroundProcessorDelay" property in Configuration Reference. The default
delay is 10 seconds. Though I think that the thread might be stuck somewhere,
as it performs other tasks as well (e.g. autodeployment).


3. You have to find a proof that there indeed are sessions that have "last
accessed time" more than (your configuration + interval between background
processing runs) ago. The manager webapp can be used to view the list of active
sessions.

It would be much better if you'd find how to reproduce this.



Note, that "Bugzilla is not a support forum". The questions on how to diagnose
something must be directed to the users@ list.

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 51835] Sessions never close

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51835

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Mark Thomas <ma...@apache.org> 2011-09-21 11:48:35 UTC ---
Session expiration is tested as part of the TCK that every Tomcat release goes
through including 6.0.29. This looks to be an application issue rather than a
Tomcat issue and - as Konstantin points out - the users list is the place to
seek help.

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org