Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 65826 invoked from network); 14 Aug 2002 16:38:37 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Aug 2002 16:38:37 -0000 Received: (qmail 14861 invoked by uid 97); 14 Aug 2002 16:38:45 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 14820 invoked by uid 97); 14 Aug 2002 16:38:44 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 14808 invoked by uid 98); 14 Aug 2002 16:38:44 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <004e01c243b0$e2732fe0$d0673240@nuserve> From: "Dan Lipofsky" To: "Tomcat Users List" References: <03d101c24375$d91f7fb0$5000a8c0@serdar> <005b01c24376$3e9c2e60$5cfaa8c0@Hornet> Subject: Re: tomcat stops randomly. why?? Date: Wed, 14 Aug 2002 09:37:31 -0700 Organization: NuServe MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-9" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I have a similar but different problem. > > Running 4.0.3 on solaris 8 standalone with jdk 1.4 > > Occasionally, tomcat dies with no error message in any log file. It is as if > someone has kill -9'ed the jvm. > > Has anyone seen anything like this? > > People here are getting very wary of tomcat. I need some resolution to this. I had something similar. The cause was an infinite JSP forward loop. Some magic caused the loop to break after 100 cycles, but sometimes the JVM experienced a seg fault instead. With a seg fault there is no chance to write anything to the log files, of course, but an error is printed to STDERR or STDOUT - we have output redirected to a file using nohup. Under Unix a core file is generated unless you turn that off (I don't know if Windows has core files) - make sure you have core file generation turned on. We are running tomcat3.2.4/jdk1.3.1 on Solaris. - Dan -- To unsubscribe, e-mail: For additional commands, e-mail: