Re: strange shut down problem

[Chris Bailey <ch...@codeintensity.com>]

You could also pipe this through "xargs kill" :)  I found this in the
archives, as I'm having the same problem.  It seems problematic to have to
do this.  Secondarily, there was another follow-up to the below thread that
said someone upgraded to JDK 1.3.1 and their problems went away.  I'm using
1.4.0 and I still see this.  I too am on Red Hat, but 7.2, and using Tomcat
4.0.3.

Has anyone seen this occurring on 4.0.4?  I haven't seen RPM's for 4.0.4
yet, so I haven't tried.

-----Original Message-----
From: Mats Nyberg
Subject: Re: strange shut down problem
Date: Wed, 22 May 2002 00:55:56 -0700
Subject: Re: strange shut down problem

and a guru told me to

  [tim-mn@spiderman src]$ ps -Af|awk '{ if ($3 == "1") { print ; } }'
|grep $JAVA_HOME|awk '{ print $2}'

you probably could backtick the whole line and issue kill on it,
provided you don't have any
conflicting java stuff going on that gets killed in the process.

Mats Nyberg wrote:

> i have the same problem (found out yesterday).
>
> it might be specific to/when running with IBM JDK (don't know).
> what i did so far was
>
>    [tim-mn@spiderman src]$ ps -efd|grep tomcat.home
>
> find the %JAVA_HOME%/bin/java -Dtomcat.home ... process with PPID = 1
> (the mother of devil's spawn)
> and KILL IT!!!
>
>    [tim-mn@spiderman src]$ kill 6203 # e.g.
>
> gurus do this in one line. as i said: found out about 9 hours ago
> slept since ;)
>
> Cindy Ballreich wrote:
>
>> I've got Tomcat 4.0.3 on Redhat 7.1 and when I start it I get the
>> usual batch of 20-50 threads. When I shut tomcat down (using
>> shutdown.sh) there are about a dozen threads that don't go away.
>> Tomcat is definately not running (at least it's not accepting
>> requests), but the threads are still there. I'm not seeing any
>> errors, but I'm not sure where to look. I've done some web searches
>> of the archives and haven't found anything, but I'm hoping that
>> someone will recognize this problem and point me in the right direction.
>>
>> Thanks!!
>>
>> Cindy
>>

____
Chris Bailey       mailto:chris@codeintensity.com
Code Intensity       http://www.codeintensity.com


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: strange shut down problem

[Mark O'Driscoll <ma...@eircom.net>]

I had this problem. 

Here's the response which is correct

Howdy,
This has been discussed a bunch of times ;)  Post 4.0.1, tomcat doesn't
do a System.exit() call when shutting down.  Accordingly, if you have
created non-daemon threads, the JVM will not stop them.  If you create
such threads in your apps, it is your responsibility to stop them
properly in the destroy() methods, context destroy event (you need a
context or lifecycle listener) for this, etc.

Alternatively, you can do stuff like recording the process ID when
tomcat is started, and then killing it as part of shutdown.  There are
threads (recently) on this list about this.

Yoav Shapira
Millennium ChemInformatics


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>