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

[Joey Wang (JIRA)]

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

Joey Wang edited comment on WFLY-6173 at 9/2/16 12:48 AM:
----------------------------------------------------------

Unfortunately I found some other memory leak after undeployment. Please try to deploy  [^memory-leak_New.zip] to Wildfly 10.1.0.Final, access url http://[WF host]/memoryLeak/webresources/user. Undeploy the application, found class instances of 'person.joey.test.UserType' still in memory.
I used SQL Server 2014 as DB server to reproduce this issue, but I guess it doesn't matter which DB server is used. Please let me know if you need more information.


was (Author: joeydaowang):
Unfortunately I found some other memory leak after undeployment. Please try to deploy  [^memory-leak_New.zip] to Wildfly 10.1.0.Final, access url http://[WF host]/memoryLeak/webresources/user. Undeploy the application, found class instances of 'person.joey.test.UserType' still in memory.
I used SQL Server 2014 as DB server to reproduce this issue, but I guess it doesn't matter which DB server is used. Please let me know if you need more information.

> 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)