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)" <ji...@apache.org> on 2011/02/28 17:56:36 UTC
[jira] Created: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
JMX ObjectName name may not match the underlying managed object
---------------------------------------------------------------
Key: QPID-3090
URL: https://issues.apache.org/jira/browse/QPID-3090
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.8, 0.7, 0.6, 0.5
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
Priority: Critical
Fix For: 0.9
Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
This disconnect in naming is the cause of various issues, such as QPID-2994
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-3090:
---------------------------------
Description:
Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
This disconnect in naming is the cause of various issues, such as QPID-2486
was:
Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
This disconnect in naming is the cause of various issues, such as QPID-2994
> JMX ObjectName name may not match the underlying managed object
> ---------------------------------------------------------------
>
> Key: QPID-3090
> URL: https://issues.apache.org/jira/browse/QPID-3090
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5, 0.6, 0.7, 0.8
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: 0.9
>
>
> Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
> This disconnect in naming is the cause of various issues, such as QPID-2486
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reassigned QPID-3090:
------------------------------------
Assignee: Andrew Kennedy (was: Robbie Gemmell)
> JMX ObjectName name may not match the underlying managed object
> ---------------------------------------------------------------
>
> Key: QPID-3090
> URL: https://issues.apache.org/jira/browse/QPID-3090
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5, 0.6, 0.7, 0.8
> Reporter: Robbie Gemmell
> Assignee: Andrew Kennedy
> Priority: Critical
> Fix For: 0.9
>
>
> Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
> This disconnect in naming is the cause of various issues, such as QPID-2486
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-3090:
---------------------------------
Description:
Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
This disconnect in naming is the cause of various issues, such as QPID-2486 and QPID-3094
was:
Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
This disconnect in naming is the cause of various issues, such as QPID-2486
> JMX ObjectName name may not match the underlying managed object
> ---------------------------------------------------------------
>
> Key: QPID-3090
> URL: https://issues.apache.org/jira/browse/QPID-3090
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5, 0.6, 0.7, 0.8
> Reporter: Robbie Gemmell
> Assignee: Andrew Kennedy
> Priority: Critical
> Fix For: 0.9
>
>
> Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
> This disconnect in naming is the cause of various issues, such as QPID-2486 and QPID-3094
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000797#comment-13000797 ]
Robbie Gemmell commented on QPID-3090:
--------------------------------------
Andrew can you review please? Thanks.
> JMX ObjectName name may not match the underlying managed object
> ---------------------------------------------------------------
>
> Key: QPID-3090
> URL: https://issues.apache.org/jira/browse/QPID-3090
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5, 0.6, 0.7, 0.8
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: 0.9
>
>
> Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
> This disconnect in naming is the cause of various issues, such as QPID-2486
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
Posted by "Andrew Kennedy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kennedy resolved QPID-3090.
----------------------------------
Resolution: Fixed
Review OK
> JMX ObjectName name may not match the underlying managed object
> ---------------------------------------------------------------
>
> Key: QPID-3090
> URL: https://issues.apache.org/jira/browse/QPID-3090
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5, 0.6, 0.7, 0.8
> Reporter: Robbie Gemmell
> Assignee: Andrew Kennedy
> Priority: Critical
> Fix For: 0.9
>
>
> Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
> This disconnect in naming is the cause of various issues, such as QPID-2486 and QPID-3094
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-3090) JMX ObjectName name may not match the
underlying managed object
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-3090:
---------------------------------
Status: Ready To Review (was: In Progress)
> JMX ObjectName name may not match the underlying managed object
> ---------------------------------------------------------------
>
> Key: QPID-3090
> URL: https://issues.apache.org/jira/browse/QPID-3090
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.5, 0.6, 0.7, 0.8
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: 0.9
>
>
> Because certain characters cannot be contained in an unquoted JMX ObjectName, the broker is currently remapping these characters (in some but not all cases) to different values to avoid trying to create an MBean with an illegal ObjectName. However, this can lead to situations where the broker considered an entity (eg a queue) to have one name, but users consider it to have another because that is what is displayed as the name of its MBean.
> This disconnect in naming is the cause of various issues, such as QPID-2486
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org