Tomcat 3.3.1 stops by itself

[Attila Szegedi <sz...@freemail.hu>]

I have Tomcat 3.3.1 running on a PA RISC machine under HP-UX 11.00 OS, using
the HP-supplied 1.3.1_01 Java VM. We are experiencing that the java process
running the Tomcat exits occasionally (approximately once a week).

The real mistery is that the Tomcat apparently performs a clean shutdown -
looking at the servlet log, we see that all contexts are closed nicely and
every servlet's destroy() method gets called (there are log messages in
servlet's destroy() methods, so we see them being called).

I'd like to ask: what are the possible events that can trigger a clean
shutdown of Tomcat? I know that a signal to Ajp12 connector is one, but
nobody is executing "tomcat.sh stop". We have now disabled the Ajp12
connector and will see if we have another unexpected stop this week...

Are there other events that can cause Tomcat to perform a clean shutdown?

The webapp that runs inside the Tomcat is somewhat heavy on memory - it eats
187 megs of heap by default, but on occasional database refreshes requires
almost twice the ammount; nevertheless the server runs with -Xmx512M and we
have monitored database refreshes and they never caused the server to stop
and never required more than ~300M heap. Altough from what I understand,
even if we had an out-of-memory situation that wouldn't cause the Tomcat to
perform its shutdown sequence, would it? I mean, all those non-daemon
threads waiting for socket connection would keep the VM alive; and even if
they wouldn't I doubt we'd see a graceful exit with contexts being shut down
and servlets being destroyed pedantly.

Any help appreciated.
Cheers,
  Attila.

--
Attila Szegedi
home: http://www.szegedi.org


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>