[
https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-12446:
-----------------------------------------
Note that that duplicate discard call problem would have the effect of slowly increasing
the max size of the pool. It doesn't leak 'bad' beans into the pool though. So
I believe the size of the queue would be limited to the max # of concurrent requests, so
not a never ending leak. So perhaps that is not the cause of the reported problem.
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}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)