RE: [Wrapper-user] wrapper.shutdown.timeout properties

[v103 <v1...@za...>]

Thank you Leif.

Seems to be working good so far.   Basically the Application on JSW platform
is connected to other middleware. And sometimes the application may take
time to close down due to this dependency on middleware(When this process
has hung up for some reason).  Therefore I had to add some time to this
parameter.

Taikei Matsushita

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Monday, August 16, 2004 1:49 PM
To: wra...@li...
Subject: Re: [Wrapper-user] wrapper.shutdown.timeout properties

Matsushita-san,

>I am currently woking on with wrapper version 3.0.5(due to project 
>policy, we cannot upgrade JSW to latest version).  I had problem with 
>JVM shutting down before the application actually wants it.  I seem to 
>solve this by setting wrapper.shutdown.time.out to a relatively large
number.
>
>I have few questions about this property.
>
>1. Having set this to zero, wrapper will not shutdown JVM unless the 
>"STOPPED" packet is sent from Java side?
>  
>
That is correct.   After the Wrapper asks the application running in the 
JVM to stop, it
will wait up to "wrapper.shutdown.timeout" seconds for the WrapperManager in
the JVM to signal that the application has stopped.  This is done by sending
a STOPPED packet to the Wrapper.

By setting it to 0.  You are allowing an infinite amount of time for your
application to
stop.   If you really want a large value, I strongly suggest using a 
value like 300 (5 minutes)
rather than 0.

>2. I don't understand the difference between wrapper.shutdown.time.out 
>and wrapper.jvm.exit.timeout.  In the document, it says 
>wrapper.jvm.exit.timeout as the "later phase".  Supposely the 
>"wrapper.jvm.exit.timeout" waits for STOPPED packet, what does
wrapper.jvm.exit.timeout wait for?
>  
>
Once the Wrapper has been notified that the Application running in the JVM
has STOPPED, the Wrapper will wait "wrapper.jvm_exit.timeout" additional
seconds
for the JVM process to actually exit.   If it does not exit within the 
timeout then the
Wrapper will forcibly kill the JVM process.

If your application registers its own shutdown hooks, then it is possible
that the WrapperManager's shutdown hook could complete before yours have
completed.
In such cases, the JVM could take a while to shutdown after the STOPPED
packet
has been sent.   I'll take a look at clarifying this in the docs.

If your post your wrapper.log with wrapper.debug=true.  I may be able to
tell you which of the timeouts you need to be setting to solve your shutdown
problems.

Cheers, (Yoroshiku onegaishimasu)
Leif