Another eas way to track down a System.exit() is to replace the System class
in rt.jar with one that you modify from the source. Add a
Thread.dumpStack() to the the call. This will let you know where the
problem is in the event that it is in a third party library that you don't
have access to th
Hi
I've also had issues with Tomcat, but maybe along different lines.
I'm using a P2-400mhz with 256 meg Ram Linux (6.2) box running Tomcat as
Stand alone.
I use JMeter to pound the heck out of some servlets on the machine like
SnoopServlet, Cookie25 and a couple of other basic servlets. The mo
Do you think you could be having garbage collection issues? Are you
specifically releasing references?
-Original Message-
From: Craig Day [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 26, 2000 21:07
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: bad time with tomcat
Hi All,
Well, probably not big help to you, but I can report
my first production site running Tomcat 3.1 on Solaris
2.7 and jdk1.2 with quite a bit of load (Cocoon 1.7.4
servlet and some custom Java classes)
My machine is 1GB RAM Netra T1 machine.
--- Craig Day <[EMAIL PROTECTED]> wrote:
> Hi All,
>
: Re: bad time with tomcat
> At this point, tomcat is the least stable component in our
> environment.
Tomcats are usually pretty unstable until you get them fixed. (sorry,
couldn't help myself)
> Tomcat will die on us regularly without giving any
> hint as to why,
If you&
> At this point, tomcat is the least stable component in our
> environment.
Tomcats are usually pretty unstable until you get them fixed. (sorry,
couldn't help myself)
> Tomcat will die on us regularly without giving any
> hint as to why,
If you're not getting an exception, then I'd suspect
