[jboss-jira] [JBoss JIRA] (AS7-6849) ClassLoader memory leak with MDB

[Vlad Arkhipov (JIRA)]

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

Vlad Arkhipov commented on AS7-6849:
------------------------------------

I attached a simple test case. Steps to reproduce:
# Install JBoss 6.1.0-EAP
# Start JBoss: standalone.sh --server-config=standalone-full.xml
# Add a new JMS queue: jboss-cli.sh --file=setup.cli
# Deploy EJB archive
# Undeploy EJB archive
Then in VisualVM look up for ModuleClassLoader with MDB class loaded:
select heap.livepaths(heap.findClass("org.jboss.test.leak.MDB").loader)

{quote}Can you post any info about what is holding onto these references?{quote}
org.jboss.thread.JBossThread.contextClassLoader (default-threads-1) is holding a reference to MDB ModuleClassLoader.
                
> ClassLoader memory leak with MDB
> --------------------------------
>
>                 Key: AS7-6849
>                 URL: https://issues.jboss.org/browse/AS7-6849
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JCA
>    Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
>            Reporter: Vlad Arkhipov
>            Assignee: Jesper Pedersen
>            Priority: Critical
>         Attachments: leak.tar.gz
>
>
> There are still some references to MDB class (NOT to the *instance*) if you undeploy an archive from the AS. Sooner or later it leads to OutOfMemory Permgen exception after multiple redeployments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira