In order to perform recovery actions (e.g. restart service) the Windows Service Controller needs to detect abnormal program terminations (failures). The Service controller detects a failure if either the service process crashes or the process terminates with a non-zero exit code.
For my Java server application I want to define recovery actions for the following conditions:
1) VM crash
2) Error was thrown (e.g. OutOfMemoryError)
3) System.exit() with non-zero exit code
When using prunsrv as a wrapper, I observe the following behaviour:
1) VM crash is detected only when StartMode=jvm, otherwise the Service Controller ignores the failure situation
2) When an Error is thrown and StartMode=jvm, prunsrv does not terminate but seems to hang. Therefore, the Service Controller is not aware of the failure. For other StartModes, prunsrv terminates, but the Service Controller does not detect the failure.
3) When System.exit(42) is called, prunsrv terminates but the Service Controller does not detect the non-zero exit code. This applies for all StartModes.
It seems to me as if prunsrv always terminates with exit code zero. But I expect the following behaviour:
1) VM crash with StartMode=jvm -> OK as it is now, but with other StartModes, prunsrv should terminate with a non-zero exit code in order to indicate the abnormal termination.
2) When an Error is thrown, prunsrv should terminate with a non-zero exit code in order to indicate the abnormal termination.
3) When System.exit() is called, prunsrv should terminate with the exit code passed to System.exit() (transparent behaviour), in order to let the application indicate a failure situation.
With the current behaviour, it is not possible to let the Windows Service Controller perform recovery actions.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|233d 19h 40m||1||Mladen Turk||22/Oct/12 06:39|
|Fix Version/s||1.0.11 [ 12320061 ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|