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 2006/11/07 12:00:50 UTC

[jira] Created: (QPID-69) Race condition in Delivery Manager

Race condition in Delivery Manager
----------------------------------

                 Key: QPID-69
                 URL: http://issues.apache.org/jira/browse/QPID-69
             Project: Qpid
          Issue Type: Bug
          Components: Java Broker
    Affects Versions: M1
            Reporter: Martin Ritchie
             Fix For: M1


The delivery manager has a race condition where messages could be added to the message queue while a channel is suspended. Only to have the channel unsuspend and purge the queue before the new message makes it on to the queue. This then causes all further messages to be queue but as the channel has now been unsuspended there is now way to kick off the asynchronous delivery process.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Assigned: (QPID-69) Race condition in Delivery Manager

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/QPID-69?page=all ]

Martin Ritchie reassigned QPID-69:
----------------------------------

    Assignee: Martin Ritchie

> Race condition in Delivery Manager
> ----------------------------------
>
>                 Key: QPID-69
>                 URL: http://issues.apache.org/jira/browse/QPID-69
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M1
>            Reporter: Martin Ritchie
>         Assigned To: Martin Ritchie
>             Fix For: M1
>
>
> The delivery manager has a race condition where messages could be added to the message queue while a channel is suspended. Only to have the channel unsuspend and purge the queue before the new message makes it on to the queue. This then causes all further messages to be queue but as the channel has now been unsuspended there is now way to kick off the asynchronous delivery process.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (QPID-69) Race condition in Delivery Manager

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/QPID-69?page=all ]

Martin Ritchie resolved QPID-69.
--------------------------------

    Resolution: Fixed

SVN Rev: 472060
Checked two DeliveryManagers one using synchronisation one using a concurrent access queue. Both should solve the race condition. The Concurrent access queue can be configured not to record the queue size. This should increase performance for installations that need the throughput. Testing needs to be done to measure the actuall performance benefits between these versions.

> Race condition in Delivery Manager
> ----------------------------------
>
>                 Key: QPID-69
>                 URL: http://issues.apache.org/jira/browse/QPID-69
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M1
>            Reporter: Martin Ritchie
>         Assigned To: Martin Ritchie
>             Fix For: M1
>
>
> The delivery manager has a race condition where messages could be added to the message queue while a channel is suspended. Only to have the channel unsuspend and purge the queue before the new message makes it on to the queue. This then causes all further messages to be queue but as the channel has now been unsuspended there is now way to kick off the asynchronous delivery process.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira