RE: BUG - Now I am confused

[tomcat_sergio tomcat <to...@hotmail.com>]

I tested Thread.sleep in a simple Java standalone program and it worked on 
Win2000 Advanced Server.

Something in tomcat makes Thread.sleep not work properly. I have no clue 
what could cause that. What I can say is: Thread.sleep from 
StandardManager.java is not being wake by the JVM. Sleeps forever...

[]s

Sergio


>From: "tomcat_sergio tomcat" <to...@hotmail.com>
>Reply-To: tomcat-user@jakarta.apache.org
>To: tomcat-user@jakarta.apache.org
>Subject: RE: BUG - valueUnbound e session timeout
>Date: Sun, 08 Jul 2001 22:59:38 -0000
>
>Problem confirmed...
>
>Thread.sleep is buggy in Win2000 Advanced server. That´s what is causing 
>the
>sessions not to time out, because the monitor thread never comes back from
>its Thread.sleep.
>
>The workaround is to check all the sessions when someones logs in. Not very
>good, but thats the only choice left.
>
>I will submit this bug in the java site.
>
>[]s
>
>Sergio
>
>
>>From: "tomcat_sergio tomcat" <to...@hotmail.com>
>>Reply-To: tomcat-user@jakarta.apache.org
>>To: tomcat-user@jakarta.apache.org
>>Subject: RE: BUG - valueUnbound e session timeout
>>Date: Sun, 08 Jul 2001 20:07:52 -0000
>>
>>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 <Mi...@aswethink.com>
>>>Reply-To: tomcat-user@jakarta.apache.org
>>>To: "'tomcat-user@jakarta.apache.org'" <to...@jakarta.apache.org>
>>>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.
>>
>
>_________________________________________________________________________
>Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.