Red Hat Bugzilla – Bug 837129
[jboss-as-5] Shutdown operation is not performed if server availability can not be determined
Last modified: 2013-09-12 11:12:43 EDT
+++ This bug was initially created as a clone of JON product Bug #837126 +++
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 has been fixed. See Bug #837126. Closing...