Re: FW: General / Special cause under which TOMCAT Crash been noticed

2010-05-03 Thread David Smith
...@googlemail.com] Sent: Friday, April 30, 2010 4:38 PM To: Tomcat Users List Subject: Re: FW: General / Special cause under which TOMCAT Crash been noticed Karthik, *If* any OutOfMemoryError occurs within Tomcat, the reason for said error will be some faulty webapp, meaning it is likely to crash any

RE: FW: General / Special cause under which TOMCAT Crash been noticed

2010-05-03 Thread Karthik Nanjangude
-Original Message- From: David Smith [mailto:david.sm...@cornell.edu] Sent: Monday, May 03, 2010 5:11 PM To: Tomcat Users List Subject: Re: FW: General / Special cause under which TOMCAT Crash been noticed If your tomcat instance crashes, it'll be sudden and not anything the tomcat

RE: FW: General / Special cause under which TOMCAT Crash been noticed

2010-05-02 Thread Karthik Nanjangude
monitor for status. With regards karthik -Original Message- From: Gregor Schneider [mailto:rc4...@googlemail.com] Sent: Friday, April 30, 2010 4:38 PM To: Tomcat Users List Subject: Re: FW: General / Special cause under which TOMCAT Crash been noticed Karthik, *If* any

FW: General / Special cause under which TOMCAT Crash been noticed

2010-04-30 Thread Karthik Nanjangude
Hi for General / Special cause under which TOMCAT Crash been noticed ? This is in referral to one of the form topics raised some day's ago For JVM to restart Tomcat in 1 case when OnOutOfMemoryError was raised URL http://marc.info/?l=tomcat-userm=127119151302985w=2 Refers to

Re: FW: General / Special cause under which TOMCAT Crash been noticed

2010-04-30 Thread Bob Hall
Karthik, --- On Thu, 4/29/10 at 11:02 PM, Karthik Nanjangude karthik.nanjang...@xius-bcgi.com wrote: This is in referral to one of the form topics raised some day's ago For JVM  to restart Tomcat in 1 case  when OnOutOfMemoryError was raised URL

Re: FW: General / Special cause under which TOMCAT Crash been noticed

2010-04-30 Thread Gregor Schneider
Karthik, *If* any OutOfMemoryError occurs within Tomcat, the reason for said error will be some faulty webapp, meaning it is likely to crash any other servlet-container, too. Therefore, stick to the rules I pointed out above, and you'll be fine: Make sure you have some solutions ready in case