Re: [Wrapper-user] Timeout if wrapper dies or is killed

[Hubert F. <hub...@ab...>]

Leif,

<This is described in the documentation for that property.

I thought that I have red everything, must have overlooked this.

<  Developers may be killing the wrapper as you say.  But that is 
<abnormal behavior
< and should be handled with a good firm SMAK!  :-)

Good idea, but I will get sore muscles and called "the smacker" then
:-), maybe I should start doing this preventive.

Old habits die hard, but if people learn that wrapper takes over and
does everything 
for them, they probabely will accept it.

< If you have a dedicated JRE installation 

We have, and if somebody really want's it that way I do the copy.

< Note that you can also get the PIDs of the wrapper and java 
<processes 

Thank you for the hints

Regards

Hubert

>>> Leif Mortenson <le...@ta...> 30.01.2007 19:18 >>>
Hubert,
    True.  But in order to get the JVM to exit immediately, you would 
have to set
the ping timeout to a low value.  Doing that would cause you other 
problems as
the wrapper could start restarting the JVM under high loads.  This is 
described in
the documentation for that property.

    Developers may be killing the wrapper as you say.  But that is 
abnormal behavior
and should be handled with a good firm SMAK!  :-)  The Wrapper is 
optimized to
handle normal operation and recover cleanly where possible when 
something goes
wrong.   It will recover and clean itself up if a pesky user does what

you did.

    As for the process names.  You are correct.  For security reasons,

windows does
not provide a way to rename the process in the task manager.  It will 
always be the
name of the executable.   To work around this on systems with multiple

JVMs and
Wrappers, I have created myapp-wrapper.exe and myapp-java.exe
executables by
copying the originals.  The java.exe copy goes in the JAVA_HOME/bin 
directory
along with the original.   It is not very clean but does what you 
want.   If you have
a dedicated JRE installation that exists under the application's 
directory structure
then the copied java.exe is a little less strange.

    Note that you can also get the PIDs of the wrapper and java 
processes with the
following properties.  This will cause them to be written to the 
specified files.  You
can then compare those PIDs with those in the Task Manager. (Note you 
need to
configure the Task Manager to show PIDs)

http://wrapper.tanukisoftware.org/doc/english/prop-pidfile.html 
http://wrapper.tanukisoftware.org/doc/english/prop-java-pidfile.html 

Cheers,
Leif

da...@sm... wrote:
> 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 =20
> allow to pass without being pinged by the Wrapper. If the Wrapper
does =20
> not ping the JVM for longer than the specified timeout, it will exit
=20
> allowing the Wrapper to resynch by launching a new JVM. This also
=20
> makes sure that the JVM will exit if the Wrapper process is
terminated =20
> abnormally."
>
> I guess this fits what you are asking for.
>
> Many thanks,
>
> David Hayes
>
> Quoting Hubert Felber <hub...@ab...>:
>
>