You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/10/30 11:24:27 UTC

DO NOT REPLY [Bug 24247] New: - signal handling on Solaris 5.8

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24247>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24247

signal handling on Solaris 5.8

           Summary: signal handling on Solaris 5.8
           Product: Commons
           Version: 1.0 Alpha
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Daemon
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: peter.poloha@nextra.sk


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.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org