Re: catalina shutdown problem - waiting for instance to be deallocate d

["Craig R. McClanahan" <cr...@apache.org>]

There was a bug in the 4.0 release that made Tomcat think a servlet was
still in use when it wasn't.  I thought this was fixed in 4.0.1 -- which
are you using?

Craig


On Fri, 2 Nov 2001, Tsai, Eddie wrote:

> Date: Fri, 2 Nov 2001 14:07:33 -0600
> From: "Tsai, Eddie" <Ed...@ncslearn.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: "'tomcat-user@jakarta.apache.org'" <to...@jakarta.apache.org>
> Subject: catalina shutdown problem - waiting for instance to be
>     deallocate d
>
> i would like to stop tomcat4.0 no matter what the states of the servlets
> are. here is my situation.
>
> WHILE the LoginServlet is running, client stops the client program that
> calls the servlet. i then used 'catalina.sh stop' command to stop tomcat.
> the log then showed
>
> StandardWrapper[LoginServlet]: Waiting for 1 instance(s) to be deallocated
>
> other servlets seemed to be destroyed fine, but not this one. it looks like
> it thinks the servlet is still being used, but it is not. after waiting for
> a long time, that servlet instance is still not deallocated. so the server
> hangs.
>
> is there a way i can set the time limit to wait for a servlet to be
> deallocated? or force it to shutdown no matter what?
>
> thanks
>
> --
> To unsubscribe:   <ma...@jakarta.apache.org>
> For additional commands: <ma...@jakarta.apache.org>
> Troubles with the list: <ma...@jakarta.apache.org>
>
>


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>