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
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
]]
Sent: Tuesday, May 21, 2002 7:58 PM
To: Tomcat Users List
Subject:strange shut down problem
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
At 05:45 PM 5/21/02 -0700, Subir Sengupta wrote:
This is a documented bug. Apparently if there is a non Daemon thread
running Tomcat won't shut down cleanly.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8700
Hmmm. That sure sounds like what's happening on my system. I guess catalina.sh
) statement as the last line in
the stop method.
Subir
-Original Message-
From: Cindy Ballreich [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 22, 2002 9:01 AM
To: Tomcat Users List
Subject: RE: strange shut down problem - solution?
At 05:45 PM 5/21/02 -0700, Subir Sengupta 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
this might get you started...
run the following commands and send your output:
netstat -a
lsof | grep java
although that second one might have a lot of outputin which case look
over that to see which files, devices, and ports the JVM has open.
fillup
On 5/21/02 4:58 PM, Cindy Ballreich
Users List
Subject: Re: strange shut down problem
this might get you started...
run the following commands and send your output:
netstat -a
lsof | grep java
although that second one might have a lot of outputin which case look
over that to see which files, devices, and ports the JVM has
