[
https://issues.apache.org/jira/browse/QPID-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113444#comment-13113444
]
Gordon Sim commented on QPID-3502:
----------------------------------
On consultation with Ken, the following is preferred:
{noformat}
Index: src/qpid/broker/SessionState.cpp
===================================================================
--- src/qpid/broker/SessionState.cpp (revision 1166820)
+++ src/qpid/broker/SessionState.cpp (working copy)
@@ -346,10 +346,8 @@
}
// if the sender has requested immediate notification of the completion...
- if (requiresSync) {
+ if (requiresSync || callSendCompletion) {
sendAcceptAndCompletion();
- } else if (callSendCompletion) {
- sendCompletion();
}
}
{noformat}
> Durable messages not acked on queue-based federation route
> ----------------------------------------------------------
>
> Key: QPID-3502
> URL: https://issues.apache.org/jira/browse/QPID-3502
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.12
> Reporter: Gordon Sim
>
> - On both the source and destination broker I run:
> qpid-config add exchange topic mytopic --durable
> qpid-config add queue myq --durable
> qpid-config bind mytopic myq 'topica.*'
> - On the destination broker I run:
> qpid-route -d -s --ack 1 queue add <dest-broker> <source-broker> mytopic
> myq
> - On the source broker machine I edit the spout script to make
> messages durable and run:
> spout mytopic/topica.hello
> - On the destination broker I run:
> drain myq
> Using qpid-stat -q monitor the dequeue of messages. Durable messages are not
> dequeued, when a transient message is sent all previous messages will be
> dequeued.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
