You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <qp...@incubator.apache.org> on 2007/11/15 09:52:43 UTC
[jira] Created: (QPID-686) requeue and release should make messages
available atomically
requeue and release should make messages available atomically
-------------------------------------------------------------
Key: QPID-686
URL: https://issues.apache.org/jira/browse/QPID-686
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Reporter: Gordon Sim
Assignee: Gordon Sim
Currently released or requeued (which is now the case for rolledback messages) are pushed onto the front of the queue in reverse order so as to preserve original ordering if no subscribers are active.
Though the AMQP spec doesn't require it, it would be much better to do this atomically such that if there are active subscribers they don't receive these messages out of order w.r.t each other (though they may unavoidably be out of order w.r.t earlier deliveries).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-686) requeue and release should make messages
available atomically
Posted by "Gordon Sim (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim updated QPID-686:
----------------------------
Fix Version/s: (was: M4)
Affects Version/s: M3
> requeue and release should make messages available atomically
> -------------------------------------------------------------
>
> Key: QPID-686
> URL: https://issues.apache.org/jira/browse/QPID-686
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: M3
> Reporter: Gordon Sim
> Assignee: Gordon Sim
>
> Currently released or requeued (which is now the case for rolledback messages) are pushed onto the front of the queue in reverse order so as to preserve original ordering if no subscribers are active.
> Though the AMQP spec doesn't require it, it would be much better to do this atomically such that if there are active subscribers they don't receive these messages out of order w.r.t each other (though they may unavoidably be out of order w.r.t earlier deliveries).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.