[
https://issues.apache.org/jira/browse/QPID-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-6240:
---------------------------------
Attachment: QPID-6240-reproducer2.tar.gz
The commit fixed it so the messages now get released back to the queue and can
be delivered to consumers rather than becoming stuck
I noticed that the delivery count is not incremented though, so the
JMSRedelivered header and the JMSXDeliveryCount property on the messages doesnt
match expectation when they are consumed again. Attaching updated sample that
uses some more messages and logs out extra info.
> 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]
