Re: [Wrapper-user] How to disable wrapper stopping, when killing JVM ?

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

Martin,
The version number was important.  If you encounter problems with an old 
version
in the future, please check the release notes.
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

There was a bug fixed in 3.2.2 where the TERM signal handler was being 
disabled when
a CHLD signal was received.  This would happen when the JVM was 
restarted for any
reason.

There was also this particular bug fixed in 3.2.0 where the TERM signals 
were not being
trapped at all by the JVM process.

If you upgrade to 3.2.3, things should work correctly for you.   The 
Wrapper will restart
a JVM killed by KILL -9.  There is no way to trap that and prevent the 
JVM from being
killed.   It will however, completely ignore TERM signals so your JVM 
will never be
restarted.

Cheers,
Leif

Martin Gazak wrote:
> ---------- Original Message -----------
> From: Leif Mortenson <le...@ta...>
> To: wra...@li...
> Sent: Thu, 22 Feb 2007 10:39:07 +0900
> Subject: Re: [Wrapper-user] How to disable wrapper stopping, when killing 
> JVM ?
>
>   
>> Martin,
>> I just retested this and it is working correctly for me. Most likely,
>> this is a misunderstanding about when it is used. The wrapper's
>> sh script by default will only use the ignore signals setting when it
>> is being run as a daemon process. Ie when "start" is used, not
>> "console".
>> Let me know your use case as it may require some changes.
>>     
>
> Leif,
> thanks for the answer. I am sorry for not being precise - we start the 
> wrapper version 3.1.2 (and therefore our application) as Linux (SuSE 10.0)
> service by "start" parameter, not "console", therefore my problems are 
> related to daemon mode. 
> The start script includes the line
> IGNORE_SIGNALS=true
>
> Our wrapper.conf also includes line
> wrapper.ignore_signals=true
>
> We want to run wrapper as service and we want the JVM to be restarted by 
> wrapper no matter what signal is sent to JVM process (in this post I am not 
> speaking about signals sent to wrapper process, but signals sent to spawned 
> java process).
> Anyway "kill -9 " (SIGKILL) sent to JVM  results even now in desired 
> behaviour (wrapper detects unexpected termination of JVM and restarts it), 
> however "kill " (SIGTERM?) sent to JVM is recognized by wrapper as a signal 
> to be stopped. This stopping is what I need to change, the JVM should be 
> restarted.
>  
>   
>> If you want to ignore signals in console mode as well, you still need
>> to set the IGNORE_SIGNALS flag in the sh script to put the sh script
>> into that mode, but in your wrapper.conf file, add the following
>> property:
>> wrapper.ignore_signals=TRUE
>>     
>
> We speak about daeomon mode. We use also console mode, however only for 
> debugging.
>
> Best regards
> Martin
>