-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
-
If SFSB instances are created more than max-active-beans in the distributable-ejb subsystem introduced in JBoss EAP 8.0, they are unremoved from the heap by eviction. Repeatedly creating SFSB instances causes a memory leak despite max-active-bean being set, eventually throwing java.lang.OutOfMemoryError.
In the case of the reproduced application attached to JIRA, the heap dump when OutOfMemoryError is thrown shows a large Retained Heap of BoundedSegmentedDataContainer:
dominator_tree in Eclipse Memory Analyzer Class Name | Shallow Heap | Retained Heap | Percentage -------------------------------------------------------------------------------------------------------------------- org.infinispan.container.impl.BoundedSegmentedDataContainer @ 0xff044130| 72 | 524,322,240 | 90.75% |- java.util.concurrent.atomic.AtomicReferenceArray @ 0xfebd18c8 | 16 | 314,600,024 | 54.45% |- org.infinispan.container.entries.ImmortalCacheEntry @ 0xfefc0810 | 24 | 104,859,192 | 18.15% '- org.infinispan.container.entries.ImmortalCacheEntry @ 0xfefc14a0 | 24 | 104,859,192 | 18.15% --------------------------------------------------------------------------------------------------------------------