Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1067264

Summary: [GSS] (6.2.x) Upgrade JBoss Remoting from 3.2.18 to 3.2.19
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Osamu Nagano <onagano>
Component: RemotingAssignee: Vladimir Dosoudil <dosoudil>
Status: CLOSED CURRENTRELEASE QA Contact: Jitka Kozana <jkudrnac>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: aogburn, bmaxwell, cdewolf, dosoudil, jkudrnac, smumford
Target Milestone: CR2   
Target Release: EAP 6.2.2   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1069069 (view as bug list) Environment:
Last Closed: 2014-06-02 12:50:00 UTC Type: Component Upgrade
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: 1067260, 1069069    
Bug Blocks: 1049365    

Description Osamu Nagano 2014-02-20 03:41:27 UTC
As described in Bug 1067260, the following commit fixes the issue.

There is no corresponding JIRA, though the same fix has already been committed in the upstream as well (WildFly 8.0.0.Final/JBoss Remoting 4.0.0.Final).

Comment 1 Osamu Nagano 2014-02-20 05:08:15 UTC
Issue Description:

An EJB client on Tomcat was leaking threads like "ejb-client-context-tasks-463-thread-2" during a load test.  From a heap dump, a Set object, org.jboss.remoting3.remote.RemoteConnectionProvider.pendingInboundConnections, was holding so many IoFuture objects.  I found a related fix on the Set object between JBoss Remoting 3.2.18 (bundled with EAP 6.2.0 and CP01) and 3.2.19.  That is only the major fix between those versions.  The customer tested with JBoss Remoting 3.2.19 and corresponding jboss-client.jar, and confirmed the leak resolved.

Comment 4 Jitka Kozana 2014-03-05 13:31:56 UTC
Verified on 6.2.2.CP.CR2.