You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2009/08/16 23:18:14 UTC
[jira] Commented: (QPID-2039) the JMX ConnectorServer is not closed
during shutdown of the JMXManagedObjectRegistry
[ https://issues.apache.org/jira/browse/QPID-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743901#action_12743901 ]
Robbie Gemmell commented on QPID-2039:
--------------------------------------
The customisations made through constructing the RMIConnectorServer instance manually to allow locking the RMIRegistry down from any RMI based modifications and binding the ConnectorServerStub to it manually when calling cs.start() also ensure that the cs.stop() method does not try and unbind the ConnectorServerStub using RMI. As a result, a simple cs.stop() call is all that is required here.
> the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry
> -------------------------------------------------------------------------------------
>
> Key: QPID-2039
> URL: https://issues.apache.org/jira/browse/QPID-2039
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2.1, M3, M4, 0.5
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.6
>
>
> the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org