[Wrapper-user] Wrapper shuts down on Linux

[David H. <dho...@gm...>]

I am using the wrapper on Linux running as a daemon.  For some reason after
running for a while (few days) it shuts down.  Here is the log:

INFO   | jvm 1    | 2008/08/31 15:22:52 |
--------------------------------------
ERROR  | wrapper  | 2008/09/02 07:49:32 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2008/09/02 07:49:33 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2008/09/02 07:49:40 | Launching a JVM...
ERROR  | wrapper  | 2008/09/02 07:50:10 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2008/09/02 07:50:10 |
ADVICE | wrapper  | 2008/09/02 07:50:10 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2008/09/02 07:50:10 | Advice:
ADVICE | wrapper  | 2008/09/02 07:50:10 | The Wrapper consists of a native
component as well as a set of classes
ADVICE | wrapper  | 2008/09/02 07:50:10 | which run within the JVM that it
launches.  The Java component of the
ADVICE | wrapper  | 2008/09/02 07:50:10 | Wrapper must be initialized
promptly after the JVM is launched or the
ADVICE | wrapper  | 2008/09/02 07:50:10 | Wrapper will timeout, as just
happened.  Most likely the main class
ADVICE | wrapper  | 2008/09/02 07:50:10 | specified in the Wrapper
configuration file is not correctly initializing
ADVICE | wrapper  | 2008/09/02 07:50:10 | the Wrapper classes:
ADVICE | wrapper  | 2008/09/02 07:50:10 |
com.dhs.service.JavaServiceWrapperWebServiceLauncher
ADVICE | wrapper  | 2008/09/02 07:50:10 | While it is possible to do so
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2008/09/02 07:50:10 | classes to make this
initialization processes automatic.
ADVICE | wrapper  | 2008/09/02 07:50:10 | Please review the integration
section of the Wrapper's documentation
ADVICE | wrapper  | 2008/09/02 07:50:10 | for the various methods which can
be employed to launch an application
ADVICE | wrapper  | 2008/09/02 07:50:10 | within the Wrapper:
ADVICE | wrapper  | 2008/09/02 07:50:10 |
http://wrapper.tanukisoftware.org/doc/english/integrate.html
ADVICE | wrapper  | 2008/09/02 07:50:10 |
------------------------------------------------------------------------
ADVICE | wrapper  | 2008/09/02 07:50:10 |
ERROR  | wrapper  | 2008/09/02 07:50:11 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2008/09/02 07:50:11 | JVM received a signal SIGKILL (9).
STATUS | wrapper  | 2008/09/02 07:50:16 | Launching a JVM...
ERROR  | wrapper  | 2008/09/02 07:50:46 | Startup failed: Timed out waiting
for a signal from the JVM.
ADVICE | wrapper  | 2008/09/02 07:50:46 |

What may be causing this?  I am not a Linux guur.  I have used the wrapper
on Windows with no issues.  My code to handle controlEvents is:

if (WrapperManager.isControlledByNativeWrapper()) {
                // The Wrapper will take care of this event
            } else {
                // We are not being controlled by the Wrapper, so
                //  handle the event ourselves.
                if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || (event
== WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event ==
WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) {
                    log.warn("We are handling the received event ourselves
and we are stopping the service");
                    WrapperManager.stop(0);
                }
            }

I am using the wrapper integrated, that is I implement WrapperListener
interface.

Since I am running as a daemon, I don't want this to ever shut down, and if
does for some reason I would like it to auto restart (don't know how to do
this on Linux).

Why might I be getting these JVM appears hung: Timed out waiting for signal
from JVM. errors?

-Dave