Re: [Wrapper-user] Error message from wrapper launching log

[Leif M. <lei...@ta...>]

Ming,
What version of the Wrapper are you using?   It is difficult to say
exactly what is happening unless you enable the Wrapper's debug output
with wrapper.debug=true.

The Wrapper is killing the JVM because it is not receiving any
response from the JVM for more than the ping timeout which defaults to
30 seconds.   This is usually because the JVM is frozen, but it can
also happen if the Java process is being starved of CPU or IO.  The
most common is due to heavy disk swapping due to low memory.   Of
course when this happens, the JVM and your application will be
unresponsive for this time but if you really want to allow this then
you can extend the ping timeout.  This is a work around, but such long
JVM freezes are usually indicative of another problem:
http://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html

Cheers,
Leif

On Fri, Jun 17, 2011 at 5:21 AM, Chen, Ming Ming <min...@hp...> wrote:
> Hi,
> I got the following error message in the wrapper log file for my application. This is the first time I see this kind message, why do I get this message? I don't think that my application/JVM was hung, it was running based on the messages in my own log file from my application.. My application/jvm was killed and restarted. Why does this happens.?
> Thanks in advance for your help.
> Regards
> Ming
>
>
> =========================
> STATUS | wrapper  | 2011/06/13 10:48:05 | Launching a JVM...
> INFO   | jvm 1    | 2011/06/13 10:48:06 | WrapperManager: Initializing...
> ERROR  | wrapper  | 2011/06/13 10:53:54 | JVM appears hung: Timed out waiting for signal from JVM.
> ERROR  | wrapper  | 2011/06/13 10:53:55 | JVM did not exit on request, terminated
> STATUS | wrapper  | 2011/06/13 10:54:00 | Launching a JVM...
> INFO   | jvm 2    | 2011/06/13 10:54:01 | WrapperManager: Initializing...
> STATUS | wrapper  | 2011/06/13 10:54:38 | <-- Wrapper Stopped
> STATUS | wrapper  | 2011/06/13 14:06:00 | --> Wrapper Started as Console