[jboss-jira] [JBoss JIRA] (WFLY-12446) Memory leak in StatelessSessionComponent
[
https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin...
]
Matěj Novotný commented on WFLY-12446:
--------------------------------------
[~brian.stansberry] in CDI + EJB integration, all stateless beans are {{@Dependent}} from
CDI perspective. And in this case there is {{Instance<X>}} used to resolve these
dependent instances. In such case user is responsible for disposing them properly. So some
of this logic should be there, not sure it's correct though, looking at it now.
I am running the reproducer locally right now.
Memory leak in StatelessSessionComponent
----------------------------------------
Key: WFLY-12446
URL: https://issues.jboss.org/browse/WFLY-12446
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, EJB
Affects Versions: 17.0.1.Final
Reporter: Joerg Baesner
Assignee: Cheng Fang
Priority: Major
Attachments: dump-weld.png, playground-jee8.zip, server.log.gz,
wfly-12446-heap-dump.png
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)