|
From: <da...@sm...> - 2007-01-30 16:23:55
|
Hub, A stab at the docs offers this page: http://wrapper.tanukisoftware.org/doc/english/prop-ping-timeout.html "This same property also controls the amount of time that the JVM will =3D20 allow to pass without being pinged by the Wrapper. If the Wrapper does =3D20 not ping the JVM for longer than the specified timeout, it will exit =3D20 allowing the Wrapper to resynch by launching a new JVM. This also =3D20 makes sure that the JVM will exit if the Wrapper process is terminated =3D20 abnormally." I guess this fits what you are asking for. Many thanks, David Hayes Quoting Hubert Felber <hub...@ab...>: > Hello, > >> From the doc: > [quote] > The WrapperManager inside the Java process reacts to the loss of the > Wrapper by assuming that it is abandoned. This leads to the JVM being > shutdown cleanly 30 seconds after the Wrapper process died. > [/quote] > > Is there a way to configure this timeout? People (specially developers) > tend to kill programs via task- or processmanager. We probabely will > have a renamed wrapper.exe for every service to be able to identify them > in the process list. So it's easy to kill a service but hard to find > the belonging java.exe that still runs for 30 seconds. > > IMHO if wrapper.exe doesn't run anymore, the belonging java service > should shutdown cleanly as soon as possible, without additional > timeout. > > hub > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share yo= ur > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DD= EVDEV > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |