Bug 1318926

Summary:	[GSS](6.4.z) Client Hang due to Long Default Read Timeout in LargeMessageControllerImpl
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tom Ross <tom.ross>
Component:	JMS	Assignee:	Tom Ross <tom.ross>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.4.5	CC:	bmaxwell, jmesnil, jtruhlar, msochure, pmackay, rnetuka
Target Milestone:	CR1
Target Release:	EAP 6.4.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1318928, 1320133, 1324262, 1325387

Description Tom Ross 2016-03-18 07:44:03 UTC

The code in LargeMessageControllerImpl.java uses TimeUnit.SECONDS instead of TimeUnit.MILLISECONDS
currentPacket = packets.poll(readTimeout, TimeUnit.SECONDS);

Comment 1 JBoss JIRA Server 2016-03-18 10:54:51 UTC

Tom Ross <toross> updated the status of jira HORNETQ-1516 to Coding In Progress

Comment 4 JBoss JIRA Server 2016-04-14 07:25:07 UTC

Tom Ross <toross> updated the status of jira HORNETQ-1516 to Resolved

Comment 5 Peter Mackay 2016-06-28 17:36:21 UTC

Verified with EAP 6.4.9.CP.CR2

Comment 6 Petr Penicka 2017-01-17 12:57:08 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.

Comment 7 Petr Penicka 2017-01-17 12:57:52 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.

Comment 8 Petr Penicka 2017-01-17 12:58:11 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.