tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl" <c...@etrak-plus.com>
Subject Re: Tomcat dies suddenly
Date Fri, 12 Feb 2010 19:55:24 GMT
Konstantin,

Your response provides some interesting ideas.

Remember that I had tried shutting Tomcat down by killing (kill -9 xxx where 
xxx is the process id) the java process and saw the same ending in the logs 
that I have been seeing when the system 'fails'.  So it would seem that I 
could test the implementation of Chris' and Peter's ideas by simply killing 
the java process and see what the debugging code gives me.  At least that 
looks like a baseline.

Thanks for the help.

Carl


----- Original Message ----- 
From: "Konstantin Kolinko" <knst.kolinko@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Friday, February 12, 2010 1:17 PM
Subject: Re: Tomcat dies suddenly


2010/2/12 Carl <carl@etrak-plus.com>:
> More details: the Dell 105 has an AMD processor and (currently) 8 GB 
> memory.
> The T110 has a Xeon 3440 processor and 4 GB memory. The current Java
> version is 1.6.0_18-b07. The current Tomcat version is 6.0.24.

Actually, 6.0.24 version *will* exit silently if it is terminated by a 
signal.

To reproduce (on Windows):
1. Run Tomcat in a console window.
2. Press Ctrl+C
3. Tomcat shutdowns in several seconds, cleanly, but silently.

That is because in 6.0.24 a VM shutdown hook was added that cleanly
terminates logging subsystem (flushing all cached messages).

The VM starts all shutdown hook threads at the same time and they run
in parallel. Thus if Tomcat is being stopped through a hook, the
logging subsystem has a chance to be already shut down at that time.

I think that the same silent shutdown will occur if calling
System.exit(), by the same reason.

I do not know, what will happen if running Tomcat with jsvc on a Unix.
(IIRC, jsvc calls the stop method in Bootstrap/Catalina, so Tomcat
shuts down not through a hook and all messages should be present).


The above is specific to 6.0.24.  In 6.0.20 logs are forcibly flushed
after each message is written, and log files are never explicitly
closed.


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message