[
https://issues.jboss.org/browse/REMJMX-59?page=com.atlassian.jira.plugin....
]
Rob Stryker commented on REMJMX-59:
-----------------------------------
Using alpha2 libraries. Seems we're still using the old url. String url =
"service:jmx:remoting-jmx://" + s.getHost() + ":" + port;
Guess I'll need to work this change of url into our code.
REMJMX support on wildfly's new management port 9990
----------------------------------------------------
Key: REMJMX-59
URL:
https://issues.jboss.org/browse/REMJMX-59
Project: Remoting JMX
Issue Type: Feature Request
Components: Connection
Reporter: Rob Stryker
Assignee: Darran Lofthouse
In Wildfly alpha2, I am unable to make a connection on port 9990. Only connections via
port 9999 work. However, other issues in wildfly fail on port 9999 and only succeed on
9990, making it hard for tools to decide which port to standardize on.
Here's the stacktrace, but I'm not sure you'll get much out of it:
{code}
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at
org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:221)
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:146)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:97)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
at
org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:70)
... 6 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira