Chuck,
Yes, it seems to point in that direction as we have ruled out most of the
rest of the universe. I am hoping I can see failure at the point of failure
with the heap dump options
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/usr/local/tomcat/logs
but I have no experience with them so I am not certain what I might see. On
Saturday, when I was stress testing it (JMeter), I was able to run it out of
memory but it still didn't die, just kept logging that it was out of memory.
Not quite square one because we have eliminated some possibilities.
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 4:04 PM
Subject: RE: Tomcat dies suddenly
From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly
I added the print options in the hope that I could see
something right at the time of failure.
Since the failures occurred before the print options were used, I guess that
rules out any possibility of the OS getting upset at the JVM calling for
timing information. Back to square one, where the most likely culprit is
still the Linux OOM killer.
- 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
