Bug 1011994

Summary: RBAC: Thread leak in domain mode processes due to address validation
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brian Stansberry <brian.stansberry>
Component: Domain ManagementAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED CURRENTRELEASE QA Contact: Ladislav Thon <lthon>
Severity: urgent Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: dosoudil, emuckenh, jcechace, myarboro, rsvoboda
Target Milestone: ER4   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:13:41 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:    
Bug Blocks: 1010473, 1010672    

Description Brian Stansberry 2013-09-25 13:57:55 UTC 
Description of problem:

The fix for https://bugzilla.redhat.com/show_bug.cgi?id=1010672 introduce a per-management request leak in slave HostController processes when common requests (e.g. read-resource) are proxied to the slave from the master. I believe the same leak will occur on domain servers for requests proxied from the HostController.

Over time this will result in OOME situations due either to the memory resources used by the threads, or because user process count limites are reached. (For example, on Linux each thread counts as a process.)

Version-Release number of selected component (if applicable):

6.2.0.ER3

How reproducible:

Against the master host controller, execute a series of /host=<nameofslave>:read-resource operations. Monitor the thread count (e.g. using jconsole) on the slave HC process and watch it go up.


We have a fix for this already in the process of getting merged into WildFly master.
Comment 2 Rostislav Svoboda 2013-09-26 10:49:49 UTC 
Hi, we think it's Beta Blocker too. We hit this problem with WebConsole experiments on ER3 build.
Comment 4 Jakub Cechacek 2013-10-04 11:00:48 UTC 
Verified for 6.2.0.ER4

Tests previously failing due to this issue passed. After looking at threads through visual vm I consider this fixed.