The new default behavior of waiting for the Java process to terminate as long as necessary was chosen because
the alternative would be to stop the wrapper, which would negate any possibility of restarting the application.
In most cases this property should not need to be adjusted. Setting it too short could have adverse affects.
In almost all cases the system will be able to forcibly terminate a process, assuming it has access to do so.
We received reports from a couple users on Windows where a request to terminate a frozen JVM process was returning successfully, but the JVM process was never actually being terminated.
This unfortunately is an unrecoverable state for the Wrapper.
Implementation of this property was done to allow the Wrapper to accurately explain the problem in the logs and then shutdown cleanly.
wrapper | Timed out waiting for the OS to forcibly terminate the JVM process, unable to continue.
wrapper | The scheduled restart of the JVM has been cancelled.
If you see this problem, please contact support about it as we are interested in finding an environment where it can be reproduced reliably.
The Java Service Wrapper provides a full set of configuration properties that allows you to make the Wrapper meet your exact needs.
Please take a look at the documentation for the individual properties to see all of the possibilities beyond the examples shown above.