Bug 1113242

Summary: [GSS] (6.4.0) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: JMXAssignee: Brad Maxwell <bmaxwell>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bmaxwell, hrupp, jmartisk, kkhan, ksuzumur, onagano, sjadhav
Target Milestone: DR3   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previous versions of JBoss EAP 6 contained several hard-coded JMX connection timeouts. In this release of the product, those intervals can now be configured via a system property or properties passed in when creating the JMXConnectorFactory: `JMXConnectorFactory.connect(serviceURL, environment);` The order of priority of these settings is as follows: * The default is 30 seconds * The Env map property overrides default * The system property overrides values passed into the env map Order of specificity: Specific timeout properties: * Channel timeout: `org.jboss.remoting-jmx.timeout.channel` * Connection timeout: `org.jboss.remoting-jmx.timeout.connection` * Versioned Connection timeout: `org.jboss.remoting-jmx.timeout.versioned.connection` If the `org.jboss.remoting-jmx.timeout` property is set and the specific property is not set, the generic value will be used instead of the default.
 Story Points: ---
Clone Of:
: 1113247 (view as bug list) Environment:
Last Closed: 2019-08-19 12:41:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1113247, 1113249    

Description Brad Maxwell 2014-06-25 17:35:28 UTC 
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)
Comment 1 Darran Lofthouse 2014-07-08 13:31:11 UTC 
*** Bug 1045311 has been marked as a duplicate of this bug. ***
Comment 2 JBoss JIRA Server 2014-08-21 20:48:53 UTC 
Brad Maxwell <bmaxwell> updated the status of jira REMJMX-86 to Resolved
Comment 4 Jan Martiska 2014-10-01 10:57:49 UTC 
Verified in EAP 6.4.0.DR3