I am using jdk1.3.1
I did some dubugging with the tomcat sources, and it seens that the problem
has to do with the Thread.sleep of StandardManager.java. This thread just
checks for expired sessions.
The thread is not waking up. Sometimes it does wake up, but most of the time
it doesnīt. Perharps the behavior of Thread.sleep in Win2000 is buggy.
I will implement the session checker myself and increase its priority. Letīs
see whether that is going to solve this annoying problem.
With WinNT this do not happen.
[]īs
Sergio
>From: Michael Wentzel <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: RE: BUG - valueUnbound e session timeout
>Date: Sun, 8 Jul 2001 12:02:49 -0400
>
> > There is a bug in Tomcat 3.2.2.
> >
> > The session is not timing out and valueUnbound is not being
> > called, even
> > with setMaxInactiveInterval(10).
> >
> > This bug only happens in windows 2000.
> >
> > Pretty annoying stuff...
>
>I run windoze2000 and tomcat 3.2.2 and do not have this problem.
>I've never checked, explicitly, if valueUnbound is getting called
>but the session timeout event does occur so I just take the specs
>word for it that valueUnbound get called(since I don't do anything
>special with SessionEvents).
>
>Are you sure this is what is happening? What, exactly, is the
>action you take and the behavior that leads you to believe this is
>what is happening? What JDK( Sun/IBM/1.? ) are you using?
>
>
>---
>Michael Wentzel
>Software Developer
>Software As We Think - http://www.aswethink.com
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
