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 (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/27 23:41:49 UTC
[jira] [Resolved] (QPID-3867)
AMQQueueMBean#clearQueue|moveMessages|copyMessages should be certain to
rollback transactions in the event of exception
[ https://issues.apache.org/jira/browse/QPID-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-3867.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.15
I'm just closing this out. If the queue depth check ever starts being a problem im happy that its an easy NO-JIRA fix.
> AMQQueueMBean#clearQueue|moveMessages|copyMessages should be certain to rollback transactions in the event of exception
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3867
> URL: https://issues.apache.org/jira/browse/QPID-3867
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.15
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: 0.15
>
>
> AMQQueueMBean#clearQueue|moveMessages|copyMessages all leave open that possibility that a LocalTransaction goes uncommitted (or unrolledback) in the event of exception.
> This will lead to uncontrolled store growth when used with BDB as would block the action of the cleaner thread.
> A finally block should be used to ensure that transaction is rolled back on any exception.
>
--
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
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org