activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1738) Messages stuck in a queue don't get dispatch (happens when consumers close out)
Date Mon, 08 Sep 2008 17:01:52 GMT

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

Gary Tully resolved AMQ-1738.
-----------------------------

    Fix Version/s: 5.2.0
                       (was: 5.3.0)
       Resolution: Fixed

this is fully nailed in 5.2, dispatch is now very tight.

> Messages stuck in a queue don't get dispatch (happens when consumers close out)
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-1738
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1738
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 5.2.0
>
>
> We have a small timing windows when we closed out the consumer were we take messages
it had 'locked' (so that other consumer don't get the same message) and unlock them so that
they are available for dispatch. During that window after we unlock those messages, we might
still be concurrently sending messages to that subscription. The messages that get sent to
the sub after we unlock are the messages that get stuck.

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


Mime
View raw message