|
From: Leif M. <le...@ta...> - 2004-08-16 14:31:58
|
Taikei, The shell script does not read the Wrapper.conf file at all. When you shutdown the Wrapper using the shell script, it has its own 5 minute timeout after which the script kills the Wrapper process. This was done to prevent the system from having problems shutting down. You can extend that time by changing the "300" in the shell script to a larger value. But if your application is taking longer than 5 minutes to shutdown cleanly after being requested to do so, then you probably have other problems that should be fixed. :-) It would add a great deal of complexity to the shell script to have it use the wrapper.jvm_exit.timeout value from the wrapper.conf file. To date, I have not heard any other complaints about the 5 minute timeout in the shell script. After timing out however, the Wrapper process is killed forcibly. If possible, a clean shutdown would be better there. So I am open to suggestions. Cheers, Leif v103 wrote: >Leif, I have a question regarding wrapper.sh. > >There is a section in wrapper.sh(AIX version) that forces to kill the >process "kill -9 $pid". >It tells if["X$pid" != "X" ] and then "kill -9 pid". > >Does this take effect regardless "wrapper.shutdown.timeout" is set to zero. > > >Taikei Matsushita > > |