You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2017/11/14 14:48:01 UTC

[jira] [Closed] (DAEMON-67) signal handling on Solaris 5.8

     [ https://issues.apache.org/jira/browse/DAEMON-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Thomas closed DAEMON-67.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.2

> signal handling on Solaris 5.8
> ------------------------------
>
>                 Key: DAEMON-67
>                 URL: https://issues.apache.org/jira/browse/DAEMON-67
>             Project: Commons Daemon
>          Issue Type: Bug
>    Affects Versions: 1.0 Alpha
>         Environment: Operating System: Solaris
> Platform: Sun
>            Reporter: Peter Poloha
>             Fix For: 1.0.2
>
>         Attachments: ASF.LICENSE.NOT.GRANTED--jsvc-unix.diff
>
>
> in the handler() function (jsvc-unix.c) is after catching the relevant signal
> the flag stopping set and the handler tries to call itself once again (over the
> func.pointer handler_xxx). In this case, the stop/restart daemon doesn't work
> correctly on Solaris, and ends with a status 143 (129) instead of 0 (123),
> without calling a java_stop()/java_destroy(). 
> If those duplicate calls from handler are removed, the daemon stop/restart works
> fine and correct.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)