Tomas,
To be fair, you did say JVM shutdown, not Tomcat shutdown.
> AFAIK Tomcat does not call System.exit() - at least did not in version
> 4.1.*, when we solved the very same problem.
Here:
>> At JVM shutdown, the JVM is terminated only if all remaining running
>> threads are daemon threads.
You've also got other candidates such as database connections, JMS
connections etc which could spawn threads (For example, for keep-alive
functionality).
The easiest thing to do is a thread dump (send the process a SIGQUIT
signal) after stopping tomcat to see which thread(s) are keeping the JV
AFAIK Tomcat does not call System.exit() - at least did not in version
4.1.*, when we solved the very same problem.
T.
Christopher
Schultz
To the best of my knowlege, System.exit() is never called from within
tomcat. Tomcat closes it's own daemon threads and then exits normally
like any other java program. If a third party package starts it's own
thread, that package is responsible for cleaning up what it starts.
Tomcat won't e
Tomas,
> At JVM shutdown, the JVM is terminated only if all remaining running
> threads are daemon threads.
Not true. System.exit() kills the VM regardless of the presence of
non-daemon threads.
-chris
signature.asc
Description: OpenPGP digital signature
At JVM shutdown, the JVM is terminated only if all remaining running
threads are daemon threads.
Therefore, if the application starts own threads, it is necessary to ensure
that
1) either all these threads are destroyed before JVM shutdown by calling
the stop() method for each of the threads,
2)
Hello,
If your servlet(s) start new threads that run independently of request
this may happen.
Could this be the case?
On Wed, October 18, 2006 01:42, Elaine TING wrote:
> Hi,
>
> This is what I have done:
>
> 1) use shutdown.sh to shut down tomcat
> 2) Now the website appears to be down
> 3) U
Elaine,
> 1) use shutdown.sh to shut down tomcat
> 2) Now the website appears to be down
> 3) Use ps -ef | grep tomcat to check the processes, tomcat still appears
> to be running:
I suspect that you are seeing another Tomcat process that is either left
over from a previous configuration (say, yo
Hi,
This is what I have done:
1) use shutdown.sh to shut down tomcat
2) Now the website appears to be down
3) Use ps -ef | grep tomcat to check the processes, tomcat still appears
to be running:
> ps -ef | grep tomcat
root 21892 1 1 14:30 pts/21 00:00:17 /local/Java/bin/java
-Djava.e
