I had face the same problem, OOME sometimes "kill" tomcat connector.
I setup two connectors (HTTP and AJP), while one connector was "dead", the other still "alive", and I could access manager/status from the "live" one to watch the "dead" one's status. I think it is tomcat's bug Leon Rosenberg-3 wrote: > > Hi, > > one of my customers recently increased amount of memory they use, so > OOME are happening more often. Most of them however do no harm, since > just the request is aborted, but the container remains functional and > next request wents well (they have a throughput of >100MB per second > in young generation so chances are good next request will get some > memory again). > > However, this exception killed tomcat completely (no replies anymore): > > Sep 30, 2007 6:56:51 PM > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run > SEVERE: Caught exception (java.lang.OutOfMemoryError: Java heap space) > executing [EMAIL PROTECTED], > terminating thread > > Any opinions, is that a bug in tomcat or is it inescapable after an OOME? > > regards > Leon > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/OOME-crushing-tomcat-tf4545506.html#a13120810 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
