Re: [Wrapper-user] Disabling JVM ping

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

Nathan,
    Does your application output large amounts of output to the console? 
 There was bug
that would cause the native side of the Wrapper to spend too much time 
processing
input from the JVM and forget about doing its other jobs.  This was 
causing timeouts
like you mentioned below.   It actually had nothing to do with pinging 
that is why
changing the ping timeout had no effect for you.
    I fixed this in 3.0.1 that was just released a couple days ago. 
 Could you please give
that version a try and get back to me about whether or not it fixes your 
problem.
    Be sure to return any modified timeouts to their default values.
    Also note that there were some changes with the scripts and config 
file in the 3.0.0
release.  You should no longer set the pid in the wrapper conf file.  It 
is now handled
from within the shell scripts.  This was done to reduce the number of 
things that a
user has to modify.

Cheers,
Leif

Clement, Nathan wrote:

>Hi,
>
>I've been using wrapper 2.2.9 and have found that it sometimes restarts the
>JVM incorrectly under heavy load.  I have set wrapper.ping.timeout to 0, but
>it still restarts the application with the following messages in the log
>(note these occur a few seconds apart - i have trimmed the irrelevant parts
>of the log):
>
>Wrapper Process has not received any CPU time for 123 seconds.  Extending
>timeouts.
>
>The Wrapper code did not ping the JVM for 40 seconds.  Quit and let the
>wrapper resynch.
>
>Wrapper Process has not received any CPU time for 57 seconds.  Extending
>timeouts.
>
>JVM exited unexpectedly.
>
>Is there a way to completely disable the pinging/automatic restarting
>functionality? - it seems to be causing us many more problems than it could
>solve.  Our JVM is quite stable and we have experienced no hanging problems
>at all.
>
>Here is the wrapper.conf file:
>
<clip>