You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "john dunning (JIRA)" <qp...@incubator.apache.org> on 2010/02/17 21:42:27 UTC
[jira] Updated: (QPID-2409) "qpid-route route map" can list the
same broker multiple times
[ https://issues.apache.org/jira/browse/QPID-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
john dunning updated QPID-2409:
-------------------------------
Attachment: qpid-route.diff
The attached (nearly trivial) patch fixes the simple case of the bug, where localhost aliases to something else.
There's a rather larger issue here, in that when you have a family of brokers who do not share the same namespace, you'll get different results depending on who's asking the question. I don't see a way to fix that in the general case other than to introduce a more global naming scheme, which is distinct from anything to do with hostname or IP address.
I don't propose to fix that right now.
> "qpid-route route map" can list the same broker multiple times
> --------------------------------------------------------------
>
> Key: QPID-2409
> URL: https://issues.apache.org/jira/browse/QPID-2409
> Project: Qpid
> Issue Type: Bug
> Environment: Should be any
> Reporter: john dunning
> Attachments: qpid-route.diff
>
>
> In the case of multi-homed brokers (i.e. that can be addressed by more than one
> name/address), the route-map feature of qpid-route can list the same broker
> more than once. This is because it indexes its list of brokers by the URL (not
> the broker's uuid).
> Version-Release number of selected component (if applicable):
> 1.1.6 / 1.2
> How reproducible:
> 100%
> Steps to Reproduce:
> 1. Start two brokers on your local system (ports 5672 and 10000)
> 2. Create a bidirectional set of dynamic federation routes:
> $ qpid-route dynamic add localhost localhost:10000 amq.topic
> $ qpid-route dynamic add localhost:10000 localhost amq.topic
> 3. View the route map:
> $ qpid-route route map
> Finding Linked Brokers:
> localhost:5672... Ok
> localhost:10000... Ok
> Dynamic Routes:
> Exchange amq.topic:
> localhost:10000 <=> localhost:5672
> Static Routes:
> none found
> 4. View the map again using the ethernet hostname (i.e. not "localhost")
> $ hostname
> dhcp-100-18-254.bos.redhat.com
> $ qpid-route route map dhcp-100-18-254.bos.redhat.com
> Finding Linked Brokers:
> dhcp-100-18-254.bos.redhat.com:5672... Ok
> localhost:10000... Ok
> localhost:5672... Ok
> Dynamic Routes:
> Exchange amq.topic:
> localhost:10000 => dhcp-100-18-254.bos.redhat.com:5672
> localhost:5672 <=> localhost:10000
> Static Routes:
> none found
> Actual results:
> Note the fact that three brokers are listed in the second map. This is
> incorrect because "dhcp-100-18-254.bos.redhat.com:5672" and "localhost:5672"
> are different names for the same broker. This causes confusion in the display
> of the routes themselves.
> Expected results:
> The first map is correct.
--
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