Chuck,
Thanks for your reply.
I only added those options recently (over the weekend) so they were not
there at the time of the last failure. Without them, the GC pauses are
insignificant. I added the print options in the hope that I could see
something right at the time of failure. The concurrent options can probably
go as I don't see they are of any value.
Thanks,
Carl
----- Original Message -----
From: "Caldarale, Charles R" <chuck.caldar...@unisys.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Wednesday, February 03, 2010 3:28 PM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
I have now added some java options:
-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/usr/local/tomcat/logs
If you can think of any rock I might look under
I would try running without concurrent GC and the PrintGC options and see if
the failures disappear. (Obviously, that will take some time before any
confidence can be had.) Hopefully, the resulting GC pause times won't be a
significant problem.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
