Re: [Wrapper-user] JVM restart with ping-timeout

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

Madis,
    Looking at your logs, the JVM is receiving pings from the Wrapper 
process
correctly, but it does not appear to be sending the ping reply back to 
the Wrapper.

    This is what a single ping cycle should look like:
---
DEBUG  | wrapperp | send a packet PING : ping
INFO   | jvm 1    | Received a packet PING : ping
INFO   | jvm 1    | Send a packet PING : ping
DEBUG  | wrapperp | read a packet PING : ping
---

    But from your logs, you are only seeing the first two lines:
---
DEBUG  | wrapperp | 2007/03/14 14:13:22 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:22 | Received a packet PING : ping
DEBUG  | wrapperp | 2007/03/14 14:13:26 | send a packet PING : ping
INFO   | jvm 1    | 2007/03/14 14:13:26 | Received a packet PING : ping
---

    Reviewing the source, I can not think of any reason why this would 
happen
repeatedly.  There are event callbacks, but if the thread was getting 
stuck there
somehow, you would not see the second fourth line.

    Are you using an unmodified version of the wrapper jar?  I ask 
because of
the lines like the following in the log:
---
INFO   | jvm 1    | 2007/03/14 14:13:17 | Received a packet PROPERTIES : 
(Property Values)
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_ARCH->x86
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_BITS->32
INFO   | jvm 1    | 2007/03/14 14:13:17 | java 
props:set.WRAPPER_FILE_SEPARATOR->\
INFO   | jvm 1    | 2007/03/14 14:13:17 | java props:set.WRAPPER_OS->windows
---
    From their timing in the log, they are being printed before your 
application has
been started and must be being displayed from within the internal
WrapperManager.readProperties method.  That is not output that was in 
the original
source.

Cheers,
Leif


madis wrote:
> Hi
>
> Altough the system is practically idle I often get VM restarts beacuse 
> the ping request times out. I have set the timeout for 4 minutes with
> wrapper.ping.timeout=240
> wrapper.ping.interval=5
>
> Does anybody know how to fix this problem without disabling VM restarts?
>
> Madis
>
>
> Here is the logfile for an example restart:
>   
<snip>