You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/04/09 11:42:12 UTC
[jira] Assigned: (QPID-1794) BaseTransactionLog does not clear the
dequeueMap in the StoreContext after processing non-transactionally
[ https://issues.apache.org/jira/browse/QPID-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1794:
------------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Hi Aidan can you review this change please.
> BaseTransactionLog does not clear the dequeueMap in the StoreContext after processing non-transactionally
> ---------------------------------------------------------------------------------------------------------
>
> Key: QPID-1794
> URL: https://issues.apache.org/jira/browse/QPID-1794
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Aidan Skinner
> Priority: Blocker
> Fix For: 0.5
>
>
> Summary:
> When processing a dequeue, non-transaction, of a message that is on multiple queues the dequeueMap on the StoreContext is not cleared after processing.
> Either processDequeues should remove the message as it processes them or context.commitTransaction() should be called afterwards to clear the map. As the Context is bound to the session it should only be accessed by one thread at a time so either approach will be safe.
> With our future goal of renaming StoreContext to Transaction and having all operations go through this object rather than directly to the TransactionLog it may make sense to have the messageIDs removed as they are processed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org