[QPID-4164] management move/copy and max delivery attempt functionality fail to properly move/copy the message if it was loaded from the message store at startup

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.16
• Fix Version/s: 0.18
• Component/s: Broker-J
• Labels: legacy-jmx-console
• Assignee: Robbie Gemmell
• Reporter: Keith Wall
• Created: 23/Jul/12 16:03
• Updated: 14/Mar/17 17:01
• Resolved: 30/Jul/12 13:44

Description

The JMX moveMessage/copyMessage functions fail to properly move/copy the message if the message has been recovered from the store at Broker startup. The Broker permanently loses the message's payload.

If an operator subsequently tries to view the problematic message with the Management interfaces, a JMX thread will be put into an infinite loop (see QPID-4170) and this will require a Broker restart.

This problem does not affect messages sent during the lifetime of the Broker's execution (they can be moved or copied as normal). The existence of messages with lost payload within the Broker does not affect the flight of other messages through the Broker.