You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mladen Turk (JIRA)" <ji...@apache.org> on 2012/11/21 09:53:58 UTC

[jira] [Updated] (DAEMON-258) prunsrv to block until start method returns

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

Mladen Turk updated DAEMON-258:
-------------------------------

    Priority: Minor  (was: Major)
    
> prunsrv to block until start method returns
> -------------------------------------------
>
>                 Key: DAEMON-258
>                 URL: https://issues.apache.org/jira/browse/DAEMON-258
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Procrun
>    Affects Versions: 1.0.10
>         Environment: Windows all versions
>            Reporter: Ian Beaumont
>            Priority: Minor
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Currently, when starting a windows service from the service control panel based on prunsrv using the JVM.dll the start method is called in a separate thread.  Upon calling this thread, the service is marked as "started" in the service control panel.  This is confusing, as if something goes wrong in the program start-up sequence (e.g. a database connection is unavailable) then the program will fail to start successfully but the user will not get any indication of this (they have to press "refresh" in the windows services window to see the service failed to start).
> It would be better to have an option to report the "service" as "starting" while the "start" method is running and only when the method returns, mark the service as "started" or "stopped" depending on a return code from the "start" method.

--
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