Description of problem: Calling shut down operation on stopped eap has different result when stopping via JMX and shutdown.sh script. When using JMX the result is 'Failed', when using shutdown.sh the result is 'Success' Version-Release number of selected component (if applicable): Version: 3.1.1.CR2 Build Number: 779662a:4c4ed8a How reproducible: Always Steps to Reproduce: 1. eap 5.1.2 is imported to JON inventory and is stopped 2. call shutdown operation (navigate to eap resource->Operations tab->schedules->new) 3. check operation result (history tab) 4. change method of shutting down from JMX (default) to shutdown.sh script (navigate to eap resource->Inventory tab->Connection settings->Shutdown Method) and provide path to shutdown.sh (Shutdown Script field in Connection settings) 5. repeat step 2 6. check operation result Actual results: operation result (step 3) is Failed operation result (step 6) is Success Expected results: operation result (step 6) is Failed with some informative error message Additional info: Exit code of shutdown.sh when calling on already stopped eap server is 1 so it shouldn't be marked as Successful.
http://git.fedorahosted.org/cgit/rhq/rhq.git/diff/?id=feb01f4 fixed in master time: Mon Oct 1 14:15:15 2012 +0200 commit: feb01f468685e7cedfa0938b759cc3a4102f9b1d author: Jirka Kremser - jkremser message: [BZ 857423 - [EAP 5.1.2] inconsistent result of shut down operation when using JMX and shutdown.sh script and server is already stopped.] Check for return code was added.
Verified on Version: 4.6.0-SNAPSHOT Build Number: 2b908fa
Bulk close of old bugs in VERIFIED state.