Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Tomcat service crashes "unexpectedly", no trace in logs
Date: Fri, 14 Jan 2005 20:04:10 +0100
Message-ID: <511E05382CC2264DB883A018856E41431F125C@HUSEXV01.dolmen.be>
Thread-Topic: Tomcat service crashes "unexpectedly", no trace in logs
Thread-Index: AcT6a9QZCt89MFyJRsW0Exh4s9ZSEQ==
Sensitivity: Personal
From: "David Vandaele" <David.Vandaele@dolmen.be>
To: <tomcat-user@jakarta.apache.org>

Hi,

We're experiencing Tomcat crashes during stresstesting of a =
webapplication.=20

Situation: Tomcat runs as a Windows service.  During stresstests the =
Tomcat-services suddenly ends "unexpectedly".  The Windows eventlog logs =
states something like: "...service ended unexpectedly..."  The problem =
is not easily or consistently reproducable...

When I look at all the logs of Tomcat and of our webapplication, no =
mention of an exception or error or crash whatsoever !(?)  (They all =
just stop abruptly)

First I thought it was an OutOfMemoryError problem.  I forced an =
OutOfMemoryError myself by limiting the memory of the JVM of Tomcat =
severely.  But then I could see loggings of an OutOfMemoryError in the =
Tomcat stderr-log, which is not what I expected because I didn't expect =
any loggings of a crash at all...

The problem only *seems* to occur when the servermachine is completely =
left alone (not logged in or locked)  Additionally, it usually occurs =
after between 30-70 minutes or so.  When I keep monitoring the machine =
while the same tests are running the crash doesn't seem to occur ?!  =
Could it be a power-saving issue, like e.g. with the network-adaptor ?  =
Then I would not expect a crash, but a stacktrace ?

I tried adding a try-catch(Throwable) around a method where everything =
starts (the process method of my Struts ActionServlet). I've been trying =
to reproduce the problem since, but as I mentioned, it's not =
consistently reproducable...

I've searched the net trying to find related problems, or a JVM problem =
of some kind with this version, haven't been successful though...  If it =
is a problem with bad memory, I would expect to see different behaviour, =
like more random crashes, not only of the Tomcat service...=20

Environment: Tomcat 4.1.29, JDK 1.4.2_03, Windows 2000ProSP4, =
bi-processor Xeon machine.

Any help/advice/ideas is really welcome and appreciated !

Kind regards,

David

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org