+++ This bug was initially created as a clone of Bug #1113242 +++ Remoting JMX has 3 hard coded 5 second timeouts which are too low and will cause timeouts such as shown below: java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:244) java.io.IOException: Timeout out waiting for header, status=WAITING at org.jboss.remotingjmx.VersionedConectionFactory.createVersionedConnection(VersionedConectionFactory.java:74)
Brad Maxwell <bmaxwell> updated the status of jira REMJMX-86 to Resolved
https://issues.jboss.org/issues/?jql=fixVersion%20%3D%201.1.3.CR1%20AND%20project%20%3D%20REMJMX shows fix for this and small testsuite fix. QE is acking.
Verified in EAP 6.3.2.CR1.