activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Commented: (AMQ-1738) Messages stuck in a queue don't get dispatch (happens when consumers close out)
Date Wed, 21 May 2008 13:48:55 GMT


Gary Tully commented on AMQ-1738:

Just a thought, this looks similar to 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:
>             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.

View raw message