You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <qp...@incubator.apache.org> on 2010/04/19 14:17:50 UTC
[jira] Created: (QPID-2517) Proposed change to QMF schema for the
broker
Proposed change to QMF schema for the broker
--------------------------------------------
Key: QPID-2517
URL: https://issues.apache.org/jira/browse/QPID-2517
Project: Qpid
Issue Type: Improvement
Components: C++ Broker, Java Broker
Reporter: Ted Ross
Assignee: Ted Ross
Priority: Minor
I would like to make a change to the management schema for the broker. A patch will be attached.
The current schema causes the "broker" object to be indexed by the TCP port. This is a problem in clusters where each node in the cluster may have a different port. Since the port is part of the index, and the index is used as the QMFv2 object identifier, method calls addressed to the broker may not be handled uniformly by each node in a cluster.
The change removes the "index" status from the "port" attribute and adds a new index attribute called "name". This name is fixed as "amqp-broker". This is a safe thing to do as there is only one broker associated with the broker-resident agent.
--
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] Commented: (QPID-2517) Proposed change to QMF schema for the
broker
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858870#action_12858870 ]
Rob Godfrey commented on QPID-2517:
-----------------------------------
If we are changing this anyway, it would be convenient if we could allow the broker to report multiple ports (since the Java Broker at least can run that way)... ultimately I think a broker may have many "transports", each "transport" will define a protocol (e.g. TCP), port, protocol version(s) that it supports, etc... This is certainly a better model of how the java broker is configured.
> Proposed change to QMF schema for the broker
> --------------------------------------------
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Java Broker
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Attachments: broker-idx.diff
>
>
> I would like to make a change to the management schema for the broker. A patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port. This is a problem in clusters where each node in the cluster may have a different port. Since the port is part of the index, and the index is used as the QMFv2 object identifier, method calls addressed to the broker may not be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a new index attribute called "name". This name is fixed as "amqp-broker". This is a safe thing to do as there is only one broker associated with the broker-resident agent.
--
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] Commented: (QPID-2517) Proposed change to QMF schema for the
broker
Posted by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860335#action_12860335 ]
Rafael H. Schloming commented on QPID-2517:
-------------------------------------------
I'd go ahead and commit this as an interim fix, but leave the JIRA open so Rob can comment when he gets back.
> Proposed change to QMF schema for the broker
> --------------------------------------------
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Java Broker
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Attachments: broker-idx.diff, java.diff
>
>
> I would like to make a change to the management schema for the broker. A patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port. This is a problem in clusters where each node in the cluster may have a different port. Since the port is part of the index, and the index is used as the QMFv2 object identifier, method calls addressed to the broker may not be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a new index attribute called "name". This name is fixed as "amqp-broker". This is a safe thing to do as there is only one broker associated with the broker-resident agent.
--
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-2517) Proposed change to QMF schema for the
broker
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross updated QPID-2517:
---------------------------
Attachment: java.diff
Patch to the Java broker to adapt to this change.
> Proposed change to QMF schema for the broker
> --------------------------------------------
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Java Broker
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Attachments: broker-idx.diff, java.diff
>
>
> I would like to make a change to the management schema for the broker. A patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port. This is a problem in clusters where each node in the cluster may have a different port. Since the port is part of the index, and the index is used as the QMFv2 object identifier, method calls addressed to the broker may not be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a new index attribute called "name". This name is fixed as "amqp-broker". This is a safe thing to do as there is only one broker associated with the broker-resident agent.
--
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-2517) Proposed change to QMF schema for the
broker
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross updated QPID-2517:
---------------------------
Attachment: broker-idx.diff
> Proposed change to QMF schema for the broker
> --------------------------------------------
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Java Broker
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Attachments: broker-idx.diff
>
>
> I would like to make a change to the management schema for the broker. A patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port. This is a problem in clusters where each node in the cluster may have a different port. Since the port is part of the index, and the index is used as the QMFv2 object identifier, method calls addressed to the broker may not be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a new index attribute called "name". This name is fixed as "amqp-broker". This is a safe thing to do as there is only one broker associated with the broker-resident agent.
--
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] Commented: (QPID-2517) Proposed change to QMF schema for the
broker
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860245#action_12860245 ]
Ted Ross commented on QPID-2517:
--------------------------------
Rob,
I like your suggestion about transports/endpoints. This is a better model for the C++ broker as well since it supports TCP, SSL, and rdma transports simultaneously.
Would you object if I commit the attached Java patch as an interim step toward making the more involved changes?
-Ted
> Proposed change to QMF schema for the broker
> --------------------------------------------
>
> Key: QPID-2517
> URL: https://issues.apache.org/jira/browse/QPID-2517
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Java Broker
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Attachments: broker-idx.diff, java.diff
>
>
> I would like to make a change to the management schema for the broker. A patch will be attached.
> The current schema causes the "broker" object to be indexed by the TCP port. This is a problem in clusters where each node in the cluster may have a different port. Since the port is part of the index, and the index is used as the QMFv2 object identifier, method calls addressed to the broker may not be handled uniformly by each node in a cluster.
> The change removes the "index" status from the "port" attribute and adds a new index attribute called "name". This name is fixed as "amqp-broker". This is a safe thing to do as there is only one broker associated with the broker-resident agent.
--
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