]
Brian Stansberry commented on WFLY-12446:
-----------------------------------------
Perhaps the problem is here:
The inner catch block discards and then the outer one discards again. Only one bean got
removed from the pool (i.e. the StrictMaxPool.pool ConcurrentLinkedQueue) but the
semaphore gets decremented twice.
Memory leak in StatelessSessionComponent
----------------------------------------
Key: WFLY-12446
URL:
https://issues.jboss.org/browse/WFLY-12446
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 17.0.1.Final
Reporter: Joerg Baesner
Assignee: Cheng Fang
Priority: Major
Attachments: playground-jee8.zip
When running the attached reproducer application and doing a memory analysis afterwards,
it looks like a memory leak, e. g.
{code}
One instance of
"org.jboss.as.ejb3.component.stateless.StatelessSessionComponent" loaded by
"org.jboss.modules.ModuleClassLoader @ 0x5e0fbc2e0" occupies 936,593,520
(96.13%) bytes. The memory is accumulated in one instance of
"java.util.concurrent.ConcurrentLinkedQueue$Node" loaded by "<system
class loader>".
{code}