[jboss-jira] [JBoss JIRA] (WFLY-6801) EJBClientContext leak: EJBClientContext is not unregistered from TCCLEJBClientContextSelectorService when it's closed
David Lloyd (JIRA)
issues at jboss.org
Thu Mar 1 09:26:01 EST 2018
[ https://issues.jboss.org/browse/WFLY-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Lloyd resolved WFLY-6801.
-------------------------------
Fix Version/s: 11.0.0.Final
(was: 9.x.x TBD)
Resolution: Done
This should be fixed in the new client in WF 11+.
> EJBClientContext leak: EJBClientContext is not unregistered from TCCLEJBClientContextSelectorService when it's closed
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6801
> URL: https://issues.jboss.org/browse/WFLY-6801
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.2.Final
> Environment: one standalone wildfly on windows7
> Reporter: liang cheng
> Labels: EJBClientContext, naming
> Fix For: 11.0.0.Final
>
>
> After running our code with several days, we found there are many EJbClientContext instances are cached in the heap and could not be GC. And cause the memory leak issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list