|
From: Leif M. <lei...@ta...> - 2012-02-08 18:06:02
|
Fabio, Thank you for the configuration file. It looks like you have it set up correctly. There are a couple things to keep in mind. 1) There are two components which are being monitored. a) The first is the JVM itself. Many JVM problems can be monitored, detected, and recovered by the Wrapper process. In these cases, the wrapper.ntservice.recovery.* properties are not used. b) The second is if the Wrapper process itself crashes. This is rare, but if it did happen, then the Windows Service Manager can make use of the settings in the wrapper.ntservice.recovery.* properties to restart the Wrapper process as a service and thus make sure your service stays up and running. 2) The wrapper.ntservice.recovery.* properties are available in the Standard and Professional editions. wrapper.tanukisoftware.com/doc/english/prop-ntservice-recovery.html How are you running your tests? Is it a test of the JVM crashing or the Wrapper? Cheers, Leif 2012/2/9 Fábio Braga de Oliveira <gtc...@cf...>: > Hello list! > > I´m trying to put my java application to run as a Windows Service, and I > would like to make this service very fail safe. For this, I´m evaluation the > Java Service Wrapper, and trying to configure the Windows to restart the > service if it fails (using the recovery tab in the service configurations), > but without success. > > My question is: What are the requirements/parameters to achieve this > requirement? I already tryied the integration methods 1 and 3, but for now I > don´t now what´s the right return code to force a automatic restart. > > My wrapper.conf is attached. > > Thank you in advance for any help! |