[
https://issues.apache.org/jira/browse/QPID-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112508#comment-16112508
]
Chris Richardson commented on QPID-7876:
----------------------------------------
[~gsim] Did you notice my comment in the PR about bridge naming? As stated I
wasn't sure how to construct a unique name so I <ahem> basically made something
up. It just so happened that it independently almost matched the implementation
in Broker::createName.
Considerations were:
* the name can't start with QPID_NAME_PREFIX ("qpid.") (enforced by broker)
* Uniqueness should probably be consistent with the route matching pattern
(link, src, dest, key, src_local). This is not the case in Broker::createName
which does not use src_local. However I don't think that that implementation is
used any more (kind != ENCODED_IDENTIFIER_V1)...
> qpid-route does not properly consider src-local when matching bridges
> ---------------------------------------------------------------------
>
> Key: QPID-7876
> URL: https://issues.apache.org/jira/browse/QPID-7876
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: qpid-cpp-1.36.0
> Reporter: Chris Richardson
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> qpid-route does not properly consider src-local when matching bridges. The
> practical upshot of this is that it may consider routes to be duplicates when
> they are in fact not.
> Take the following (slightly contrived) scenario:
> Brokers A and B both have queues named "test.queue" and default exchanges
> named "amq.direct".
> We would like a queue route to pull messages from B:test.queue to
> A:amq.direct and a src_local route to push messages from A:test.queue to
> B:amq.direct. Since qpid-route does not consider the src-local flag, it will
> regard the second route to be a duplicate and will not allow it to be added.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
