You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Armin Noll (JIRA)" <qp...@incubator.apache.org> on 2010/02/03 15:45:27 UTC
[jira] Created: (QPID-2385) Qpid C++ broker: delivery property
Qpid C++ broker: delivery property
-----------------------------------
Key: QPID-2385
URL: https://issues.apache.org/jira/browse/QPID-2385
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Environment: Red Hat Enterprise MRG 1.2
Reporter: Armin Noll
Priority: Minor
Consider the following scenario:
- start two clustered brokers (B1 and B2) with durable queue Q and durable topic exchange E (the configuration of queues, exchanges and bindings must be persistent)
- create binding between Q and E for all messages
- start a consumer application C, connect it to B2, waiting for messages in queue Q
- start a publisher application P, connect it to B1, start continuous message transfer to exchange E
- stop broker B2
- P is still connected to B1 and is publishing messages
- start broker B2
- reconnect C to B2
The first N messages received by C after the reconnect are missing the delivery property "exchange".
--
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] Updated: (QPID-2385) Qpid C++ broker: delivery property
Posted by "Armin Noll (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Armin Noll updated QPID-2385:
-----------------------------
Description:
Consider the following scenario:
- start two clustered brokers (B1 and B2) with durable queue Q and durable topic exchange E (the configuration of queues, exchanges and bindings must be persistent)
- create binding between Q and E for all messages
- start a consumer application C, connect it to B2, waiting for messages in queue Q
- start a publisher application P, connect it to B1, start continuous message transfer to exchange E
- stop broker B2
- P is still connected to B1 and is publishing messages
- start broker B2
- reconnect C to B2
The first N messages received by C after the reconnect are missing the delivery property "exchange".
This problem has also been reported as Red Hat service request #1991690.
was:
Consider the following scenario:
- start two clustered brokers (B1 and B2) with durable queue Q and durable topic exchange E (the configuration of queues, exchanges and bindings must be persistent)
- create binding between Q and E for all messages
- start a consumer application C, connect it to B2, waiting for messages in queue Q
- start a publisher application P, connect it to B1, start continuous message transfer to exchange E
- stop broker B2
- P is still connected to B1 and is publishing messages
- start broker B2
- reconnect C to B2
The first N messages received by C after the reconnect are missing the delivery property "exchange".
> Qpid C++ broker: delivery property
> -----------------------------------
>
> Key: QPID-2385
> URL: https://issues.apache.org/jira/browse/QPID-2385
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Environment: Red Hat Enterprise MRG 1.2
> Reporter: Armin Noll
> Priority: Minor
>
> Consider the following scenario:
> - start two clustered brokers (B1 and B2) with durable queue Q and durable topic exchange E (the configuration of queues, exchanges and bindings must be persistent)
> - create binding between Q and E for all messages
> - start a consumer application C, connect it to B2, waiting for messages in queue Q
> - start a publisher application P, connect it to B1, start continuous message transfer to exchange E
> - stop broker B2
> - P is still connected to B1 and is publishing messages
> - start broker B2
> - reconnect C to B2
> The first N messages received by C after the reconnect are missing the delivery property "exchange".
> This problem has also been reported as Red Hat service request #1991690.
--
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