Bug 1113242 – [GSS] (6.4.0) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1113242 - [GSS] (6.4.0) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts [NEEDINFO]

Summary:	[GSS] (6.4.0) RemotingConnector & VersionedConectionFactory need configurable...

Status:	VERIFIED

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	JMX (Show other bugs)
Sub Component:
Version:	6.4.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR3
Target Release:	EAP 6.4.0
Assigned To:	Brad Maxwell
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	1045311 (view as bug list)
Depends On:
Blocks:	1113247 1113249
	Show dependency tree / graph

Reported:	2014-06-25 13:35 EDT by Brad Maxwell
Modified:	2018-03-06 15:38 EST (History)
CC List:	7 users (show)

See Also:
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:
Clones:	1113247 (view as bug list)
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	smumford: needinfo? (bmaxwell)

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	REMJMX-86	Major	Resolved	RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts	2017-07-31 03:05 EDT

Groups: None (edit)

Description Brad Maxwell 2014-06-25 13:35:28 EDT

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 09:31:11 EDT

*** Bug 1045311 has been marked as a duplicate of this bug. ***

Comment 2 JBoss JIRA Server 2014-08-21 16:48:53 EDT

Brad Maxwell <bmaxwell@redhat.com> updated the status of jira REMJMX-86 to Resolved

Comment 4 Jan Martiska 2014-10-01 06:57:49 EDT

Verified in EAP 6.4.0.DR3

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