Bug 1390207

Summary: [GSS] (6.4.z) Hibernate Scanner implementation class shouldn't leak application entity classes
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Stephen Fikes <sfikes>
Component: JPAAssignee: Stephen Fikes <sfikes>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Simka <msimka>
Severity: high Docs Contact:
Priority: high    
Version: 6.4.8CC: bmaxwell, jbilek, msochure, rstancel, scott.marlow, smarlow
Target Milestone: CR1   
Target Release: EAP 6.4.13   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: A class loader is created and cached for each class/interface loaded by the Hibernate scanner while inspecting a deployment archive containing a persistence unit. Consequence: For large archives (containing many classes/interfaces), an exception may occur: java.lang.OutOfMemoryError: Metaspace Fix: A single loader will be used by the Hibernate deployment scanner, per-persistence unit Result: Reduced memory footprint (for metaspace)
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-03 16:43:24 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: 1386335    

Description Stephen Fikes 2016-10-31 14:00:24 UTC 
Description of problem:
Memory growth due to creation of a class loader per class during processing of archives containing persistence units.

How reproducible:
Consistently

Steps to Reproduce:
Deploy an archive containing a persistence unit
Comment 4 Jiří Bílek 2017-01-06 10:36:04 UTC 
Verified with EAP 6.4.13.CP.CR1
Comment 5 Petr Penicka 2017-02-03 16:43:24 UTC 
Released with EAP 6.4.13 on Feb 02 2017.