[Wrapper-user] JVM can't restart

[<a.s...@aa...>]

Hello,

we are using the service wrapper with good success.
But we have one thing who troubles it a bit.

Sometimes when a JVM is killed due to out of memory errors, the JVM is=20
not restarted.
But most of the time it restarts just fine.

In the logfile we see this:

ERROR  | wrapper  | 2006/11/21 15:11:33 | JVM appears hung: Timed out=20
waiting for signal from JVM.
STATUS | wrapper  | 2006/11/21 15:11:33 | Dumping JVM state.
ERROR  | wrapper  | 2006/11/21 15:11:38 | JVM did not exit on request,=20
terminated
STATUS | wrapper  | 2006/11/21 15:11:38 | JVM exited in response to=20
signal SIGKILL (9).
ERROR  | wrapper  | 2006/11/21 15:11:38 | Unable to start a JVM
STATUS | wrapper  | 2006/11/21 15:11:38 | <-- Wrapper Stopped

In the wrapper config we have these parameters:

wrapper.request_thread_dump_on_failed_jvm_exit=3DTRUE
wrapper.restart.delay=3D15
wrapper.restart.reload_configuration=3DTRUE


What seems strange is the fact that between the "JVM exited in response=20
to signal SIGKILL (9)." and the "Unable to start a JVM" there is no 15=20
second delay. The one configured as restart.delay.

So we assume that the new JVM can't instaltly restart, because the old=20
one is not completely shutdown yet.

After such a error condition we can just restart it without any problems.

Andr=E9