[
https://issues.apache.org/jira/browse/QPID-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Harvey updated QPID-4164:
--------------------------------
Assignee: Philip Harvey (was: Keith Wall)
Status: Open (was: Ready To Review)
This issue also affected messages that the broker moved to a DLQ, so a test
should be added to check that this is fixed.
> Management moveMessage/copyMessage functions fail to properly move/copy the
> message if the message has been loaded from the store at Broker startup
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4164
> URL: https://issues.apache.org/jira/browse/QPID-4164
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Broker BDB Store, Java Management :
> JMX Console
> Affects Versions: 0.16, 0.18
> Reporter: Keith Wall
> Assignee: Philip Harvey
> Priority: Critical
> Fix For: 0.19
>
>
> 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 Broker thread will be put into an infinite loop 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
