[
https://issues.apache.org/jira/browse/QPID-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2373:
------------------------------
Fix Version/s: 0.6
> Durable exchange state not replicated to broker joining cluster
> ---------------------------------------------------------------
>
> Key: QPID-2373
> URL: https://issues.apache.org/jira/browse/QPID-2373
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.5
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
> Fix For: 0.6
>
>
> Description of problem:
> If a durable exchange exists in a cluster, and a broker joins the cluster,
> the durable exchange is not listed for the new broker.
> How reproducible:
> 100%
> Steps to Reproduce:
> 1. Start a broker in a cluster at <address1>
> 2. Run 'qpid-config -a <address1> add exchange ExDurable direct --durable'
> 3. Run 'qpid-config -a <address1> add exchange Ex direct'
> 4. Run 'qpid-config -a <address1> exchanges' to see both newly created
> exchanges
> 5. Start another broker within the cluster at <address2>.
> 6. Run 'qpid-config -a <address2> exchanges'.
> Actual results:
> The output shows only exchange 'Ex' and not 'ExDurable'.
> Expected results:
> Both exchanges should be there.
> Additional info:
> Durable queues seem to work.
> You get the same problem if you start both brokers initially, then create the
> durable exchange (it appears in both), then shut down one broker and bring it
> back up (the durable exchange disappears).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
