Bug 857070 - Add more descriptive error message when stopping aleady stopped EAP5 server via JON
Add more descriptive error message when stopping aleady stopped EAP5 server v...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Operations (Show other bugs)
4.5
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-13 09:51 EDT by Filip Brychta
Modified: 2012-10-09 14:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Filip Brychta 2012-09-13 09:51:42 EDT
Description of problem:
$Summary

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 in JON inventory and is stopped 
2. invoke 'Shut down' operation on this eap resource (navigate to resource's operation tab and create new schedule)

  
Actual results:
Operation result (in operation history tab):
java.lang.Exception: Shutting down the server using JMX failed: null
	at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)


Expected results:
i.e. Shutting down the server using JMX failed: connection refused

Note You need to log in before you can comment on or make changes to this bug.