[jira] Issue Comment Edited: (AMQ-1738) Messages stuck in a queue don't get dispatch (happens when consumers close out)

["Gary Tully (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/AMQ-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42924#action_42924 ] 

gtully edited comment on AMQ-1738 at 5/21/08 6:49 AM:
----------------------------------------------------------

Hiram,
Just a thought, this looks similar to AMQ-1714 where I though the dispatchLock held the key to subscriptions. I guess the fix for AMQ-1714 may have made the  window smaller but it is still there :-(

If you get a moment, would you cast your eye over the fix for AMQ-1714 in this context, there may be a more complete locking strategy that will close the window such that AMQ-1738 does not occur. That is, it may be possible to negate the check in add() that you just added if the dispatch locking logic is improved a bit.


      was (Author: gtully):
    Hiram,
Just a thought, this looks similar to https://issues.apache.org/activemq/browse/AMQ-1714 where I though the dispatchLock held the key to subscriptions. I guess the fix for AMQ-1714 may have made the  window smaller but it is still there :-(

If you get a moment, would you cast your eye over the fix for AMQ-1714 in this context, there may be a more complete locking strategy that will close the window such that AMQ-1738 does not occur. That is, it may be possible to negate the check in dispatch that you just added if the dispatch locking logic is improved a bit.

  
> 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.