Red Hat Bugzilla – Bug 837126
[jboss-as-5] Shutdown operation is not performed if server availability can not be determined
Last modified: 2013-09-11 07:01:14 EDT
Description of problem:
If JBoss EAP server has become unstable due to OutOfMemoryError condition or other problem that prevents the JBoss AS 5 plug-in from obtaining a connection to the server/service, it is reported as DOWN and the shutdown operation invocation does not occur even when a script is used as the shutdown method.
The result is that an unstable or runaway EAP server can not be shutdown from the JON management UI.
Version-Release number of selected component (if applicable):
If EAP resource is shown with availability of UNKNOWN or DOWN, the shutdown operation is not performed and the operation result is: The server is already shut down.
The shutdown operation should still be invoked regardless of the availability of the EAP resource.
This is due to theo rg.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate.shutDown() first retrieving the availability of the resource and if DOWN is returned, the method is aborted. This prevent a custom shutdown script from performing a forced shutdown in the event the EAP server has become unresponsive (kill -2/kill -9).
This issue prevents an alert definition from performing a resource restart in the event that something bad happens in the resource. For example, if a user wants to auto-restart a production JBoss EAP server in the event that a resource limit is reached (OOME), this issue prevents the restart from being successful.
We should take a look at this and see if there are any repercussions from removing the avail check.
Author: Lukas Krejci <firstname.lastname@example.org>
Date: Tue Aug 7 15:54:18 2012 +0200
[BZ 846269] - AS5's shutdown operation doesn't require availability to be up.
(cherry picked from commit 153be59c5228bfe4e63657da405d30b5bdb6b423)
Moving to ON_QA since JON 3.1.1 ER2 build is availble - https://brewweb.devel.redhat.com/buildinfo?buildID=228250
Verified that shutdown.sh is called even when eap availability is down. Verified on 3.1.1.CR2