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: M4, M3, M2.1, 0.5
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
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:[email protected]
