You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2010/12/14 17:21:05 UTC

[jira] Created: (AMQNET-296) Message Prioirty Support in dispatch channel can cause QueueBrowsers work incorrectly

Message Prioirty Support in dispatch channel can cause QueueBrowsers work incorrectly
-------------------------------------------------------------------------------------

                 Key: AMQNET-296
                 URL: https://issues.apache.org/jira/browse/AMQNET-296
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: ActiveMQ
    Affects Versions: 1.4.1
            Reporter: Timothy Bish
            Assignee: Timothy Bish
             Fix For: 1.5.0


When processing messages for the QueueBrowser an empty dispatch Message marks the end of the browse window but a flaw in the queuing in the dispatch channel can route this ahead of the actual Message's when the priority support is on.  The dispatch channel needs to mark this "Message" as a lower priority so that the Message queue'd ahead of it reach the QueueBrowser first.



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

[jira] Resolved: (AMQNET-296) Message Prioirty Support in dispatch channel can cause QueueBrowsers work incorrectly

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-296.
---------------------------------

    Resolution: Fixed

Fixed in trunk.

> Message Prioirty Support in dispatch channel can cause QueueBrowsers work incorrectly
> -------------------------------------------------------------------------------------
>
>                 Key: AMQNET-296
>                 URL: https://issues.apache.org/jira/browse/AMQNET-296
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>    Affects Versions: 1.4.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 1.5.0
>
>
> When processing messages for the QueueBrowser an empty dispatch Message marks the end of the browse window but a flaw in the queuing in the dispatch channel can route this ahead of the actual Message's when the priority support is on.  The dispatch channel needs to mark this "Message" as a lower priority so that the Message queue'd ahead of it reach the QueueBrowser first.

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