You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2012/07/30 15:45:34 UTC
[jira] [Resolved] (QPID-4164) Management moveMessage/copyMessage
functions fail to properly move/copy the message if the message has been
loaded from the store at Broker startup
[ https://issues.apache.org/jira/browse/QPID-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-4164.
----------------------------------
Resolution: Fixed
Assignee: Keith Wall (was: Robbie Gemmell)
> 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: Keith Wall
> Priority: Critical
> Fix For: 0.19
>
> Attachments: QPID-4164-MaxDeliveryCountTest-should-restart-broker-after-enqueue.patch
>
>
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org