Bug 1113242 - [GSS] (6.4.0) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts
Summary: [GSS] (6.4.0) RemotingConnector & VersionedConectionFactory need configurable...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMX
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR3
: EAP 6.4.0
Assignee: Brad Maxwell
QA Contact:
URL:
Whiteboard:
: 1045311 (view as bug list)
Depends On:
Blocks: 1113247 1113249
TreeView+ depends on / blocked
 
Reported: 2014-06-25 17:35 UTC by Brad Maxwell
Modified: 2020-01-02 15:14 UTC (History)
7 users (show)

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.
Clone Of:
: 1113247 (view as bug list)
Environment:
Last Closed: 2019-08-19 12:41:13 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker REMJMX-86 0 Major Resolved RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts 2020-01-02 15:14:21 UTC

Internal Links: 1045311

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
Note You need to log in before you can comment on or make changes to this bug.