commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Beaumont (JIRA)" <>
Subject [jira] [Commented] (DAEMON-258) prunsrv to block until start method returns
Date Mon, 11 Mar 2013 15:19:13 GMT


Ian Beaumont commented on DAEMON-258:

The issue is, users would always have to press "refresh" after they press "start" (otherwise
they have no idea the application has started successfully).
Maybe not a "big deal" to you, but that isn't how the majority of other services work in Windows
and therefore users would need "special" training that they need to do this.  
Start "SQL Server database service", or "Oracle Database service" - and the service will not
mark itself as "started" until it has completed successfully.  If it does take a long time
to start, "Windows" warns about this - that the service hasn't started in the expected period
of time.
Can we at least leave the issue open, as someone may either request the same feature or come
up with another way of implementing it.
> prunsrv to block until start method returns
> -------------------------------------------
>                 Key: DAEMON-258
>                 URL:
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Procrun
>    Affects Versions: 1.0.10
>         Environment: Windows all versions
>            Reporter: Ian Beaumont
>            Assignee: Mladen Turk
>            Priority: Minor
>             Fix For: 1.0.11
>   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:

View raw message