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/11/10 16:25:28 UTC

[jira] Created: (QPID-2196) JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed

JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed 
--------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: QPID-2196
                 URL: https://issues.apache.org/jira/browse/QPID-2196
             Project: Qpid
          Issue Type: Bug
          Components: Java Management : JMX Console
    Affects Versions: 0.6
            Reporter: Robbie Gemmell
            Assignee: Robbie Gemmell
            Priority: Minor
             Fix For: 0.6


The JMX Management Console may try to auto-refresh the server view between recieving notification of JMXConnector failure/closure, and the server view actually finishing being cleaned up and cleared. This can result in NullPointerException when the console tries using details of an MBean retrieved from a map that can no longer return the required details.

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


[jira] Updated: (QPID-2196) JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed

Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated QPID-2196:
---------------------------------

    Description: 
The JMX Management Console may try to auto-refresh the server view between recieving notification of JMXConnector failure/closure, and the server view actually finishing being cleaned up and cleared. This can result in NullPointerException when the console tries using details of an MBean retrieved from a map that can no longer return the required details. This can also lead to failure to properly clean up the connection tree, leaving the defunct server connection in view with the user unable to reconnect to that server without restarting the console.


  was:The JMX Management Console may try to auto-refresh the server view between recieving notification of JMXConnector failure/closure, and the server view actually finishing being cleaned up and cleared. This can result in NullPointerException when the console tries using details of an MBean retrieved from a map that can no longer return the required details.

       Priority: Major  (was: Minor)

> JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed 
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2196
>                 URL: https://issues.apache.org/jira/browse/QPID-2196
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Management : JMX Console
>    Affects Versions: 0.6
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>             Fix For: 0.6
>
>
> The JMX Management Console may try to auto-refresh the server view between recieving notification of JMXConnector failure/closure, and the server view actually finishing being cleaned up and cleared. This can result in NullPointerException when the console tries using details of an MBean retrieved from a map that can no longer return the required details. This can also lead to failure to properly clean up the connection tree, leaving the defunct server connection in view with the user unable to reconnect to that server without restarting the console.

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


[jira] Resolved: (QPID-2196) JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed

Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved QPID-2196.
----------------------------------

    Resolution: Fixed

> JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed 
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2196
>                 URL: https://issues.apache.org/jira/browse/QPID-2196
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Management : JMX Console
>    Affects Versions: 0.6
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>             Fix For: 0.6
>
>
> The JMX Management Console may try to auto-refresh the server view between recieving notification of JMXConnector failure/closure, and the server view actually finishing being cleaned up and cleared. This can result in NullPointerException when the console tries using details of an MBean retrieved from a map that can no longer return the required details. This can also lead to failure to properly clean up the connection tree, leaving the defunct server connection in view with the user unable to reconnect to that server without restarting the console.

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


[jira] Updated: (QPID-2196) JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed

Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell updated QPID-2196:
---------------------------------

    Status: Ready To Review  (was: In Progress)

> JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed 
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2196
>                 URL: https://issues.apache.org/jira/browse/QPID-2196
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Management : JMX Console
>    Affects Versions: 0.6
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>             Fix For: 0.6
>
>
> The JMX Management Console may try to auto-refresh the server view between recieving notification of JMXConnector failure/closure, and the server view actually finishing being cleaned up and cleared. This can result in NullPointerException when the console tries using details of an MBean retrieved from a map that can no longer return the required details. This can also lead to failure to properly clean up the connection tree, leaving the defunct server connection in view with the user unable to reconnect to that server without restarting the console.

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