You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Kim van der Riet (JIRA)" <qp...@incubator.apache.org> on 2010/01/28 17:51:34 UTC
[jira] Created: (QPID-2373) Durable exchange state not replicated
to broker joining cluster
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
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.
-
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] Assigned: (QPID-2373) Durable exchange state not replicated
to broker joining cluster
Posted by "Kim van der Riet (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim van der Riet reassigned QPID-2373:
--------------------------------------
Assignee: Kim van der Riet
> 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
>
> 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.
-
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] Resolved: (QPID-2373) Durable exchange state not replicated
to broker joining cluster
Posted by "Kim van der Riet (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim van der Riet resolved QPID-2373.
------------------------------------
Resolution: Fixed
Fixed in svn r.904154
> 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
>
> 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.
-
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