[QPID-8345] [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver's desired snd-settle-mode is set to settled and transactions are not used for message receiving

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4
• Fix Version/s: qpid-java-broker-7.0.9, qpid-java-broker-7.1.5
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 22/Jul/19 13:50
• Updated: 03/Apr/20 11:09
• Resolved: 06/Oct/19 10:30

Description

When receiving link desired snd-settle-mode is set to settled and transactions are not used for message receiving, the broker sending link sends the messages pre-settled.
However, the consumed messages are left in acquired state on the queue after sending them to consumer. Such messages stack in acquired state until broker is restarted. After the restart, the persistent message became available for consumption again.

The broker should remove sent pre-settled messages from the queue queue. If consumer default outcome is set explicitly to other value than accepted or null, than the transfer state should be set to accepted in order to notify the receiver about sender behaviour.