commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Beaumont (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DAEMON-258) prunsrv to block until start method returns
Date Mon, 26 Nov 2012 10:36:58 GMT

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

Ian Beaumont commented on DAEMON-258:
-------------------------------------

I'm not sure that a separate refresh thread is the solution to this problem.  The problem
is that if a user uses the "windows service control panel" to start a service (not the Apache
service configuration window) - then the service will immediately report itself as "started"
in the control panel. 

Will the separate refresh thread be able to update the status in the "windows service control
panel"?  (I'm not sure that is possible).

The way other windows services work is that they will show "starting", and only return a state
of "Started" on successful completion of the service starting. 

                
> 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

Mime
View raw message