Re: [Wrapper-user] Wrapper abnormal faileur

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

The Wrapper is shutting down because it is receiving a SIG TERM from 
someplace.
I have encountered this on Solaris systems at a customer site in the 
past.  To help track down
the source, I added more information about the source of the signal in 
the debug output.
Upgrade to 3.1.2 to try that out.   It now shows the PID of the 
application which sent
the signal.   The second pid in the output is the pid of the shell from 
which that application
was run.  In the case of scripts, the pid of the script is not all that 
useful. :-)

You can also take advantage of the new ability to ignore such signals 
and trigger a wrapper
shutdown using an anchor file instead.  Once again, upgrade to 3.1.2.  
In the new sh script,
uncomment the #IGNORE_SIGNALS=true line towards the top.   This should 
fix things
for you.

Let me know what you find out.
Cheers,
Leif

Nick Rice wrote:

>Hi,
>
>I deployed the JSW for a server application a few weeks back and its
>been working well since. I'm running Java 1.4.2 (on Linux) and Wrapper
>(JSW) 3.1.0. But for the past two days, the wrapper has been stopping on
>its own every few minutes, due to an abnormal faileur of some sort. The
>log dump is as follows:
>
>  
>
<snip>