[jira] [Commented] (DAEMON-274) procrun ignores shutdown

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (DAEMON-274) procrun ignores shutdown

Lars Bruun-Hansen (Jira)

    [ https://issues.apache.org/jira/browse/DAEMON-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542211#comment-13542211 ]

Adam Fanello commented on DAEMON-274:
-------------------------------------

Express differently, procrun registers to be told when to start and stop, but not to be told when the O/S is shutting down. So the service stops gracefully when told to stop, but not when the O/S shuts down.

Notice the IGNORES_SHUTDOWN setting when queried:

sc query myservice

SERVICE_NAME: myservice
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
               

> procrun ignores shutdown
> ------------------------
>
>                 Key: DAEMON-274
>                 URL: https://issues.apache.org/jira/browse/DAEMON-274
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.10
>         Environment: Windows OS
>            Reporter: Hsehdar
>              Labels: procrun
>
> Procrun does not gracefully shut down when OS shut down occurs. Operating system kills the service started. Service started using procrun is with state IGNORES_SHUTDOWN.
> What was expected?
> Procrun service registered to be ACCEPTS_SHUTDOWN such that procrun shuts down gracefully within the time allocated by OS.
> It would be great if this becomes command line parameter. It will be a bonus :)
> Author requests assignee to change this issue details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira