Bug 622625 - EWP 5.1.0.CR2: Shutdown fails, can't connect JMX
EWP 5.1.0.CR2: Shutdown fails, can't connect JMX
Status: CLOSED NOTABUG
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
1.3.1
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Corey Welton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-09 19:59 EDT by Ondřej Žižka
Modified: 2010-08-10 08:36 EDT (History)
0 users

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


Attachments (Terms of Use)

  None (edit)
Description Ondřej Žižka 2010-08-09 19:59:16 EDT
EWP 5.1.0.CR2  http://porkchop.devel.redhat.com/devel/candidates/JBEWP/JBEWP-5.1.0-CR2/jboss-ewp-noauth-5.1.0.CR2.zip

JON 2.4.0.GA  http://porkchop.devel.redhat.com/released/JBossON/2.4.0/GA/


STR:

1) Install & run EWP from a terminal
2) Inventorize
3) Try to shut it down or restart.
4) See the Failure:

java.lang.RuntimeException: Can not connect to the server
	at org.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate.shutdownViaJmx(ApplicationServerOperationsDelegate.java:420)
	at org.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate.shutDown(ApplicationServerOperationsDelegate.java:311)
	at org.rhq.plugins.jbossas5.ApplicationServerOperationsDelegate.invoke(ApplicationServerOperationsDelegate.java:133)
	at org.rhq.plugins.jbossas5.ApplicationServerComponent.invokeOperation(ApplicationServerComponent.java:461)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
Comment 1 Ondřej Žižka 2010-08-10 08:36:38 EDT
JBPAPP-4847

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