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/02 13:22:13 UTC
[jira] Updated: (QPID-1783) MessageFactory does not allow
TransactionLogs to recover messages out of order.
[ https://issues.apache.org/jira/browse/QPID-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1783:
---------------------------------
Status: Ready To Review (was: In Progress)
> MessageFactory does not allow TransactionLogs to recover messages out of order.
> -------------------------------------------------------------------------------
>
> Key: QPID-1783
> URL: https://issues.apache.org/jira/browse/QPID-1783
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Blocker
> Fix For: 0.5
>
>
> Summary:
> The MessageFactory is too strict, requiring messages to be recovered in order when in reality the Log will most likely process a single queue at a time.
> MessageFactory.createMessage(long,TransactionLog) should simply allow the message creation remembering the highest value received.
> Duplicate Message IDs will only occur if there is a bug in the TransactionLog. The MessageFactory will still guarantee to provide unique values by remembering the highest seen value.
--
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