[jboss-jira] [JBoss JIRA] (WFLY-6173) Classes not unloaded after undeployment

[David Maes (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13305853#comment-13305853 ] 

David Maes commented on WFLY-6173:
----------------------------------

Hello [~mkouba],

Our development team is using wildfly 10.1.0 for the moment. 
We are having the same issue described here. After multiple deploys/undeploys our server crashes with een OOM exception. The "fix version" field for this issue has not yet been set. But I'm guessing it was fixed in the 10.1.0 release. The changelog of this release did not contain the bug.

If this issue was resolved in the 10.1.0 release then I am guessing we are having another cause for the OOM. If so we will investigate and log an issue here.

 Greetings,

David 

> Classes not unloaded after undeployment
> ---------------------------------------
>
>                 Key: WFLY-6173
>                 URL: https://issues.jboss.org/browse/WFLY-6173
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld
>    Affects Versions: 8.2.0.Final, 10.0.0.Final
>            Reporter: Joey Wang
>            Assignee: Martin Kouba
>            Priority: Blocker
>         Attachments: memory-leak.zip, memory-leak_New.zip
>
>
> I deployed a small web application with one single JSF and one managed bean, accessed the page and then undeployed the application. I found the classes of this application had never been unloaded via monitoring with Java VistualVM, also using '-XX:+TraceClassUnloading' JVM option proved the classes not unloaded. 
> Then checking the heap dump of it, I found there were instance for each enum item (the managed bean has one enum type field, which is always initialized when the managed bean constructed) and one array instance including these enum instances.
> Please refer to the attachment for the same application. I started to verify the classloader memory leak issue because we found hot redeployment of our real application swallow some memory each time, then after lots of redeployment the server was short of memories.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)