You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org> on 2009/09/16 16:02:57 UTC
[jira] Resolved: (QPID-2071) JMX connections properly closed by the
server are not cleaned up by the console
[ https://issues.apache.org/jira/browse/QPID-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-2071.
---------------------------------
Resolution: Fixed
> JMX connections properly closed by the server are not cleaned up by the console
> -------------------------------------------------------------------------------
>
> Key: QPID-2071
> URL: https://issues.apache.org/jira/browse/QPID-2071
> Project: Qpid
> Issue Type: Bug
> Components: Java Management : JMX Console
> Affects Versions: M2.1, M3, M4, 0.5
> Reporter: Robbie Gemmell
> Assignee: Aidan Skinner
> Priority: Minor
> Fix For: 0.6
>
>
> In the past the JMXConnectorServer has not been stopped properly, and so only JMXConnectionNotification.FAILED notifications have been emitted by the JMXConnection in the console when the server was shut down (cleanly or otherwise). However, QPID-2039 corrects this and so when the JMXConnectorServer is stopped, it closes the client connections cleanly and causes them to emit a JMXConnectionNotification.CLOSED notification. The console only listens for JMXConnectionNotification.FAILED Notifications and as result does not clean up the connection when the server is shut down properly. Instead, the severed connection is considered ok by the console and it throws connection refused exceptions as it attempts to refresh the view using the broken connection.
--
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