[jboss-jira] [JBoss JIRA] (WFLY-12446) Memory leak in StatelessSessionComponent
Jaikiran Pai (Jira)
issues at jboss.org
Tue Sep 3 23:55:00 EDT 2019
[ https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778827#comment-13778827 ]
Jaikiran Pai commented on WFLY-12446:
-------------------------------------
[~jbaesner], would you be able to enable TRACE level logging for "org.jboss.as.ejb3" package and then attach the generated logs to this issue? If you have access to the generated heap dump file, attaching that too will help. I would have tried your reproducer, but it requires SOAP UI, which I don't have access to and I'm being lazy to set it up.
> 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)
More information about the jboss-jira
mailing list