activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason R. Theune (JIRA)" <>
Subject [jira] Reopened: (AMQ-1738) Messages stuck in a queue don't get dispatch (happens when consumers close out)
Date Fri, 27 Jun 2008 16:29:00 GMT


Jason R. Theune reopened AMQ-1738:

We are still experiencing this issue.
Our customer reports that this issue still occurs.
The problem is the locking of Messages in the queue. 
The class "IndirectMessagereference" uses the methods "lock()" and "unlock()". 
While adding Messages to the queue, messages are locked and unlocked continiously. 
When a consumer is removed, the messages locked by the consumer are unlocked. 

At this point, the race condition appears to prevent locked messges from ever being unlocked
Locked Messages cannot be retrieved from the queue by any other consumer, so they stay there

> 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