[
https://issues.apache.org/jira/browse/QPID-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318017#comment-14318017
]
Robbie Gemmell commented on QPID-6240:
--------------------------------------
This change seems to do the trick. Seem ok?
{noformat}
---
a/qpid/java/broker-plugins/amqp-1-0-protocol/src/main/java/org/apache/qpid/server/protocol/v1_0/ConsumerTarget_1_0.java
+++
b/qpid/java/broker-plugins/amqp-1-0-protocol/src/main/java/org/apache/qpid/server/protocol/v1_0/ConsumerTarget_1_0.java
@@ -426,6 +426,7 @@ class ConsumerTarget_1_0 extends AbstractConsumerTarget
modified.setDeliveryFailed(true);
_link.getEndpoint().updateDisposition(_deliveryTag, modified, true);
_link.getEndpoint().sendFlowConditional();
+ _queueEntry.incrementDeliveryCount();
_queueEntry.release();
}
}
{noformat}
> transactionally accepted messages stuck in acquired after abort
> ---------------------------------------------------------------
>
> Key: QPID-6240
> URL: https://issues.apache.org/jira/browse/QPID-6240
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.31
> Reporter: Gordon Sim
> Assignee: Rob Godfrey
> Fix For: 0.31
>
> Attachments: QPID-6240-reproducer.tar.gz,
> QPID-6240-reproducer2.tar.gz, qpid.log
>
>
> If the client/controller accepts a message under a given transaction, and at
> the same time settles that delivery (which appears from 4.4.4.2 to be a valid
> option), and the transaction is then aborted (either explicitly on request
> from controller, or by ending the session) the message remains in the
> acquired state.
> If the delivery is only accepted under the transaction, but not settled, then
> abort works as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
