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 2008/10/24 21:33:44 UTC
[jira] Resolved: (QPID-1366) C++ Broker Federation - Automatic
configuration of anti-looping
[ https://issues.apache.org/jira/browse/QPID-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross resolved QPID-1366.
----------------------------
Resolution: Fixed
> C++ Broker Federation - Automatic configuration of anti-looping
> ---------------------------------------------------------------
>
> Key: QPID-1366
> URL: https://issues.apache.org/jira/browse/QPID-1366
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: M4
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Fix For: M4
>
>
> Automatic configuration of the anti-looping (tag/exclude) mechanism.
> The anti-looping mechanism is hard to configure correctly and is arguably a detail of the brokers' implementation. It would be better if anti-looping was applied correctly without any input from the broker administrator.
> From dev-list:
> 1) Make the local tag a configuration item for the broker (vhost
> actually). The tag is a UUID and is generated automatically by the
> broker at startup. If a data-dir is supplied, the tag shall be persistent.
> 2) Add the tag to the server-properties and client-properties fields
> in the connection.start-ok and connection.start messages
> respectively. Name this property "qpid.federation_tag".
> 3) When federation routes are set up and their queues configured, if
> tag and exclude values are not supplied in the setup method
> (bridge), use the locally configured tag and the tag advertised by
> the federation peer when setting up the queue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.