Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 837126

Summary: [jboss-as-5] Shutdown operation is not performed if server availability can not be determined
Product: [JBoss] JBoss Operations Network Reporter: Larry O'Leary <loleary>
Component: OperationsAssignee: Lukas Krejci <lkrejci>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: high    
Version: JON 3.1.0CC: fbrychta, jsanda
Target Milestone: ---   
Target Release: JON 3.1.1   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 837129 846269 (view as bug list) Environment:
Last Closed: 2013-09-11 11:01:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 837129    
Bug Blocks: 846269    

Description Larry O'Leary 2012-07-02 21:35:26 UTC 
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):
3.1.0

How reproducible:
Always

 
Actual results:
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.

Expected results:
The shutdown operation should still be invoked regardless of the availability of the EAP resource.

Additional info:
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[1]. This prevent a custom shutdown script from performing a forced shutdown in the event the EAP server has become unresponsive (kill -2/kill -9).



[1]: http://git.fedorahosted.org/git?p=rhq/rhq.git;a=blob;f=modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ApplicationServerOperationsDelegate.java;h=5ac0413999c735cbd4e688d19c4089bc3b484c6c;hb=refs/heads/release/jon3.1.x#l306
Comment 1 Larry O'Leary 2012-07-02 22:05:21 UTC 
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.
Comment 2 Charles Crouch 2012-08-03 02:00:05 UTC 
We should take a look at this and see if there are any repercussions from removing the avail check.
Comment 3 Lukas Krejci 2012-08-07 14:55:31 UTC 
release/jon3.1.x http://git.fedorahosted.org/cgit/rhq/rhq.git/diff/?id=b519248ec59f0e4a403a5722f23872c96316508c
Author: Lukas Krejci <lkrejci>
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)
Comment 4 John Sanda 2012-08-14 02:16:54 UTC 
Moving to ON_QA since JON 3.1.1 ER2 build is availble - https://brewweb.devel.redhat.com/buildinfo?buildID=228250
Comment 5 Filip Brychta 2012-09-14 11:57:12 UTC 
Verified that shutdown.sh is called even when eap availability is down. Verified on 3.1.1.CR2