[
https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-12446:
-----------------------------------------
This input may be completely useless so don't assume otherwise. :)
In the source of the playground-jee8.zip in CommandServiceBean:
{code}
// avoid memory leak
logger.info("destroying commands to avoid memory leak!");
for (Command command : commands) {
commands.destroy(command);
}
{code}
The Commands themselves are all SLSBs, injected via
@Any
@Inject
Instance<Command> commands;
Maybe irrelevant, or maybe it's a normal practice I just don't know about, or
maybe it was an attempt to cure this leak that failed. But it seemed like an odd thing to
do when the Command impls are all SLSBs.
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)