Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 10 Sep 2012 22:18:07 +1100 (NCT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <1102725721.57202.1347275887813.JavaMail.jiratomcat@arcas>
In-Reply-To: <1763276261.55252.1347179947481.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-4033) AMQ Broker - Uses custom
 RMIServerSocketFactory class which cannot be unloaded due socket reuse
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451893#comment-13451893 ] 

Claus Ibsen commented on AMQ-4033:
----------------------------------

The class com.sun.rmi.transports.tcp.TCPEndpoint is having a strong reference to the org.apache.activemq.broker.jmx.ManagementContext$2 class, which is that factory class.  There is no API to unregister this factory class.
                
> AMQ Broker - Uses custom RMIServerSocketFactory class which cannot be unloaded due socket reuse
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4033
>                 URL: https://issues.apache.org/jira/browse/AMQ-4033
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMX
>    Affects Versions: 5.6.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>         Attachments: MMC.png
>
>
> When embedding ActiveMQ Broker in a container, such as Tomcat or others. And if you have JMX enabled on the broker, then a RMI registry is created to allow JMX/RMI over TCP.
> This uses a custom RMIServerSocketFactory that gets enlisted into the JDK RMI registry. But when you undeploy the AMQ broker, there is no API in the JDK to unregister your custom RMIServerSocketFactory class.
> And therefore the JDK (system class) has a strong reference to the custom RMIServerSocketFactory, which prevents the container classloader to fully unload all classes.
> Disabling JMX on the broker, allows to unload all the classes.

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