Details
Description
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.
Attachments
Issue Links
- is duplicated by
-
DAEMON-342 Procrun does not support accuratly the service lifecycle states
- Resolved