Well, for standalone Java processes, I it works.
I also start JVMs directly and they react on sigterm.
Surprising why it would not with Karaf.

-- 
Jürgen Kindler




-----Ursprüngliche Nachricht-----
Von: Achim Nierbeck <[email protected]>
Antworten an: Karaf User <[email protected]>
Datum: Tue, 16 Aug 2011 17:01:50 +0200
An: Karaf User <[email protected]>
Betreff: Re: Killing Karaf instance using sigterm (-15)

>I'm not sure if it's a bug or a feature :-)
>But I'd rather use the service wrapper for such things cause the
>service wrapper also reacts on the Sigterm signal.
>The std. shell scripts depend on java and how it handles it :-)
>
>Regards, Achim
>
>2011/8/16 JÃ1Ž4rgen Kindler <[email protected]>:
>> Hi all,
>> Trying to gracefully terminate a Karaf instance I had started on a
>>remote
>> system using the STAF process service, but Karaf does not react at all.
>> The same is true for a Karaf I start locally on a terminal and try to
>> terminate from another terminal window using kill ­15 <pid>.
>> My observation is that it does not matter whether I started Karaf with
>> ./bin/karaf or ./bin/start ­ in any case the process does not react on
>>the
>> sigterm signal.
>> Could this be a bug?
>> Cheers
>>   Jürgen
>> --
>> Jürgen Kindler
>>
>
>
>
>-- 
>--
>*Achim Nierbeck*
>
>
>Apache Karaf <http://karaf.apache.org/> Committer & PMC
>OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>Committer & Project Lead
>blog <http://notizblog.nierbeck.de/>

Reply via email to