You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Tsai, Eddie" <Ed...@ncslearn.com> on 2001/11/02 22:55:27 UTC

RE: catalina shutdown problem - waiting for instance to be deallo cate d

i was running 4.0 when i noticed the problem. i am now running 4.0.1 and
have hard time duplicating the problem. i assume that is fixed in 4.0.1. i
will keep my eye on it.

to upgrade from 4.0 to 4.0.1, i basically copied the following jar files
from 4.0.1 and left rest the same because i wanted to keep my configuration.
was that a valid way to upgrade?

i copied

bin/bootstrap.jar
common/lib/*
jasper/*
server/lib/*

thank you very much!

eddie
--


> -----Original Message-----
> From: Craig R. McClanahan [mailto:craigmcc@apache.org]
> Sent: Friday, November 02, 2001 3:10 PM
> To: Tomcat Users List
> Subject: Re: catalina shutdown problem - waiting for instance to be
> deallocate d
> 
> 
> 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
> 

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


RE: catalina shutdown problem - waiting for instance to be deallo cate d

Posted by "Craig R. McClanahan" <cr...@apache.org>.

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

> Date: Fri, 2 Nov 2001 15:55:27 -0600
> From: "Tsai, Eddie" <Ed...@ncslearn.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: 'Tomcat Users List' <to...@jakarta.apache.org>
> Subject: RE: catalina shutdown problem - waiting for instance to be
>     deallo cate d
>
> i was running 4.0 when i noticed the problem. i am now running 4.0.1 and
> have hard time duplicating the problem. i assume that is fixed in 4.0.1. i
> will keep my eye on it.
>

Cool.

> to upgrade from 4.0 to 4.0.1, i basically copied the following jar files
> from 4.0.1 and left rest the same because i wanted to keep my configuration.
> was that a valid way to upgrade?
>

In this particular case it works, but you can get bitten by unintended
changes following this pattern in general.  It's much safer to create a
new directory for the new release and them import your stuff into it,
rather than installing on top of an existing release.

> i copied
>
> bin/bootstrap.jar
> common/lib/*
> jasper/*
> server/lib/*
>
> thank you very much!
>
> eddie
> --
>

Craig


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