|
From: Patrick W. <wo...@em...> - 2004-01-13 21:58:04
|
--- Patrick Woodworth <wo...@em...> wrote: > > I using the wrapper to control an app that uses an ill-behaved > library. > I set a filter to detect the string "Out of Memory" which the > library > will spit out before it calls System.exit(). However in testing it > looks like after the filter is triggered the wrapper is being told to > shutdown and this overrides the restart behaviour. Is there any way > to > make the restart take precedence regardless of what comes later? > Okay, I've found using wrapper.disable_shutdown_hook=TRUE to be an acceptable workaround. However it would be nice if the shutdown hook could be configured to ask for a restart rather than a shutdown from the wrapper so I could still get the benefits of an orderly shutdown before restarting. |