[QPID-8432] [Broker-J][7.0.x] Message references can be leaked in some rare circumstances

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4, qpid-java-broker-7.1.5
• Fix Version/s: qpid-java-broker-7.0.9
• Component/s: Broker-J
• Assignee: Alex Rudyy
• Reporter: Alex Rudyy
• Created: 03/Apr/20 10:12
• Updated: 03/Apr/20 14:56
• Resolved: 03/Apr/20 14:55

Description

A defect was found in changes for method AbstractQueue#visit()QueueEntryVisitor introduced as part of QPID-8273. In some rare circumstance the message references can be leaked (when method #visitor() is called and entry is deleted between call to QueueEntryIterator#advance and org.apache.qpid.server.queue.QueueEntry#newMessageReference ), which could result in unexpected message references left behind. Potentially, the persistent message can be left un-deleted after removal of queue entry.

Issue Links

• is a clone of: QPID-8378 [Broker-J] Message references can be leaked in some rare circumstances