Re: [Wrapper-user] Killing Java process kills wrapper

[Richard E. <rem...@ed...>]

Setting IGNORE_SIGNALS to true in the 3.1.2 linux script does not help.
When SIGTERM is sent to the JVM,

kill java_process_id

the WrapperSimpleApp's controlEvent method is called with results in
a call to WrapperManager.stop - both JVM and Wrapper are stopped.

Richard

Leif Mortenson wrote:
> If you send a SIGTERM to the JVM, it will interpret this a CTRL-C and 
> shutdown cleanly.
> This is actually the correct behavior.   If you want the JVM and Wrapper 
> to ignore such
> signals, you can do so by setting the wrapper.ignore_signals property.  
> If you do that however,
> you should also take a look at the wrapper.anchorfile property.
> http://wrapper.tanukisoftware.org/doc/english/prop-ignore-signals.html
> http://wrapper.tanukisoftware.org/doc/english/prop-anchorfile.html
> 
> If you choose this method, then I suggest setting the IGNORE_SIGNALS 
> property in the
> 3.1.2 shell script rather than setting the properties directly.  This 
> will cause the shell script
> to cleanly start and stop the wrapper using the anchor file rather than 
> signals.
> 
> Cheers,
> Leif
> 
> Richard Emberson wrote:
> 
>> Version  3.1.2
>> OS linux
>> using WrapperSimpleApp
>>
>> killing the java process using the kill command,
>>
>>  
>>
>>> kill java_process_id
>>>   
>>
>>
>> also kills the wrapper process.
>>
>> Why?
>>
>> Thanks.
>>
>> Richard
>>  
>>
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>