|
From: Leif M. <lei...@ta...> - 2014-12-10 08:18:42
|
Steve, The Wrapper does several things to monitor the health of the Java process that it is managing. One of the simpler ones is to ping the JVM at regular intervals. The JVM then responds as soon as it sees the ping request. Newer versions of the Wrapper include a timestamp with the pings to help measure the return time. When the JVM fails to respond to a ping for longer than the wrapper.ping.timeout threshold, the Wrapper decides that the JVM is frozen and restarts it. See the following page for details: http://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html If you set wrapper.debug=true you will be able to see all of these pings and their payloads in the log file. Cheers, Leif On Tue, Dec 9, 2014 at 12:36 AM, <Ste...@su...> wrote: > Hello, > > > > Could anyone please explain how the pinger threads work? Is it as simple > as the wrapper and the wrapped JVMs communicating using port 15003? What do > these threads send to each other? > > > > Thanks, > > Steve > -- Leif Mortenson Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel: +81-3-3878-3211 Fax: +81-3-3878-0313 http://www.tanukisoftware.com lei...@ta... |