[Wrapper-user] wrapper executable fails to restart JVM

[Patrick W. <wo...@em...>]

I'm using the wrapper to run a service and I'm seeing odd behaviour on
two Solaris 8 boxes.  Basically the java process dies and goes away. 
The wrapper executable is still running but never restarts the JVM. 
This has happened on two different boxes, sometimes after running for 2
weeks and sometimes after only 21 hours or so.  Unfortunately I haven't
been able to reproduce the error with debug flags on, but below is a
snippet of what does appear in the log file.  Basically the first line
of the snippet is the last thing sent to the log before manual
intervention.  The rest of the snippet occurs after we noticed the JVM
process no longer existed and we manually told the wrapper to restart. 
Any suggestions on what this might be?

INFO | jvm 1 | 2003/12/31 10:14:43 | WebApplication: SETUP COMPLETED.
STATUS | wrapper | 2004/01/02 13:43:54 | Shutting down.
INFO | jvm 1 | 2004/01/02 13:43:54 | Wrapper Manager: The Wrapper code
did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch.
INFO | jvm 1 | 2004/01/02 13:43:54 | Stopping service Tomcat-Standalone
INFO | wrapper | 2004/01/02 13:43:54 | Wrapper Process has not received
any CPU time for 104525 seconds. Extending timeouts.
STATUS | wrapper | 2004/01/02 13:43:54 | <-- Wrapper Stopped
DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning intermediate
process...
DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning daemon process...
STATUS | wrapper | 2004/01/02 13:43:59 | --> Wrapper Started as Console