[
https://issues.apache.org/jira/browse/DAEMON-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598909#comment-13598909
]
Ian Beaumont commented on DAEMON-258:
-------------------------------------
I would suggest that this feature is only available for an "in-process" and not
a detached application. So therefore I wouldn't see the need to use IPC via
socket. This is where the user wants tight integration between the Windows
service and their Java application.
That said, for a "detached process" to currently stop, it is already left up to
the user how that happens via the "--StopImage" executable, so something
similar could potentially be used to query it's status and get a return code.
>> In case your service functionality depends on some external resource which
>> can be unavailable the standard way is to have a dependent service that will
>> either check or start that resource.
Yes, but in the real world networks go down, hard-disks fail, etc - so to work
on the assumption it can't fail just isn't possible.
> 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
> 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: http://www.atlassian.com/software/jira
