|
From: Darren <dar...@go...> - 2009-07-22 10:44:55
|
I have a java application, running under the wrapper, which is able to update itself and signal a restart to the wrapper using an exit code. Each application upgrade requires the wrapper restarts the JVM twice in quick succession. In testing I let the application upgrade itself repeatedly and it fell over at 5 restarts. Looking through the docs I see the following properties can be updated to change this. wrapper.max_failed_invocations=5 wrapper.successful_invocation_time=300 My question is, does the failed invocation count ever get reset? If not, I'm going to need to increase wrapper.max_failed_invocations based on twice the estimated number of upgrades before the physical server is restarted. Alternatively I could delay the upgrades so wrapper.successful_invocation_time passes before a restart is signalled. Either of these workarounds shouldn't be a problem, just wondering if there is another solution? Thanks, Darren |