[jira] Resolved: (QPID-572) broker delivers messages out of order

["Rob Godfrey (JIRA)" <qp...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey resolved QPID-572.
------------------------------

    Resolution: Fixed
      Assignee: Rob Godfrey  (was: Rafael H. Schloming)

Fixed by the refactoring which removed CSDM

> broker delivers messages out of order
> -------------------------------------
>
>                 Key: QPID-572
>                 URL: https://issues.apache.org/jira/browse/QPID-572
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2, M2.1, M3
>            Reporter: Rafael H. Schloming
>            Assignee: Rob Godfrey
>             Fix For: M3
>
>         Attachments: QPID-572-testcase.patch
>
>
> ConcurrentSelectorDeliveryManager will sometimes deliver messages out of order. This is caused by the code in deliver(...) that attempts to short-circuit message queuing when there is an available subscription. This code can result in the currently published message skipping ahead of queued messages causing out of order delivery. Although unrelated to transactions, I have observed this failure occuring in TransactedTest both in testCommit and testRollback. Normally it does not happen very frequently, however placing a Thread.sleep(500) in the async delivery thread will cause the failure to occur almost all the time.
> I tried fixing the problem by only attempting synchronous delivery when there are no queued messages, however this appears to break other tests that use selectors. This makes me suspect that the selector implementation is somehow incorrectly coupled to synchronous delivery.
> I have only verfied this issue on the trunk, however I believe it effects M2 as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.