Bug 1113247

Summary:	[GSS] (6.3.x) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	JMX	Assignee:	Brad Maxwell <bmaxwell>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Martiska <jmartisk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.1	CC:	hrupp, istudens, jmartisk, rsvoboda
Target Milestone:	CR1
Target Release:	EAP 6.3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1113242
Clones:	1113252 (view as bug list)		Environment:
Last Closed:	2019-08-19 12:43:03 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:	1113242
Bug Blocks:	1113251, 1113252, 1132166, 1166839

Description Brad Maxwell 2014-06-25 17:47:35 UTC

+++ 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)

Comment 1 JBoss JIRA Server 2014-08-21 20:48:52 UTC

Brad Maxwell <bmaxwell> updated the status of jira REMJMX-86 to Resolved

Comment 3 Rostislav Svoboda 2014-09-22 14:43:20 UTC

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.

Comment 4 Jan Martiska 2014-10-20 10:54:34 UTC

Verified in EAP 6.3.2.CR1.