> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: tomcat shutdown: catalina.sh STOP vs SIGTERM
>
> I'm not sure why it would take 20-30 seconds for you to see
> the above message: it should be immediate.
One possible cause is specifying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ajay,
On 3/8/2010 2:56 PM, Aggarwal, Ajay wrote:
> When I send SIGTERM to tomcat, I actually do get
>
> 1) these messages in my catalina.out
>
> Mar 8, 2010 2:46:05 PM org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
2010/3/8 Aggarwal, Ajay :
> When I send SIGTERM to tomcat, I actually do get
>
Tomcat installs a shutdown hook into JVM so that it will shutdown gracefully.
There is a problem though that if there are several shutdown hooks
then they run in parallel. That is particularly visible in 6.0.24,
becaus
---
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, March 08, 2010 1:33 PM
To: Tomcat Users List
Subject: Re: tomcat shutdown: catalina.sh STOP vs SIGTERM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ajay,
On 3/8/2010 12:53 PM, Aggarwal, Ajay wrote:
>
On Mon, Mar 8, 2010 at 9:53 AM, Aggarwal, Ajay
wrote:
> What is the downside of using SIGTERM, if any? It does seem to bring
> tomcat down in an orderly manner and much faster than "catalina.sh
> stop".
Yeah, "seem to" would be the operative phrase, I think.
A leap off a tall structure might "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ajay,
On 3/8/2010 12:53 PM, Aggarwal, Ajay wrote:
> Sometimes on a busy system I have seen that "catalina.sh stop" does take
> a long time to shutdown tomcat.
You might want to investigate why this is happening: my Tomcat instances
(we have 4 in prod
