You might want to take a look at a message I posted earlier which touches
on this issue in a Debian context and contains an example script:
http://www.mail-archive.com/jboss-user%40lists.sourceforge.net/msg07745.html
In our experience, usually jBoss will respond to SIGTERM (15) and shut
down gracefully, but sometimes it will be wedged and unresponsive. In
such cases, we need to make sure that we have the ability to shut it down,
and we need to send SIGKILL (9).
The approach I chose was to send SIGTERM and start a time-of-day limit, by
default 300 seconds (5 minutes) after the SIGTERM was sent. If that limit
was reached and jBoss was still running, it would be sent SIGKILL. Under
normal circumstances, jBoss takes about 15-20 seconds after SIGTERM to
exit completely and shut down gracefully.
-- Mike
On 2001-06-28 at 20:17 +0200, [EMAIL PROTECTED] wrote:
> On Thu, Jun 28, 2001 at 07:24:42PM +0200, Tristan Donaldson wrote:
>
> > Looking through the scripts I noticed you are shutting the server down
> > with a "kill -9". I don't think this is wise as this terminates the
> > process immediately without allowing it to close itself.
> > Changing the "kill -9" to straight "kill" fixes the problem and the
> > server seems to shutdown properly.
>
> Fixed, thank you very much.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
