activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Klaus Stake (JIRA)" <>
Subject [jira] [Commented] (AMQ-3477) Side effect when you use QueueBrowser. Missing Message in subsequent calls.
Date Tue, 30 Aug 2011 05:30:37 GMT


Klaus Stake commented on AMQ-3477:

Timothy, I am not sure if I understand you correctly. It is all stripped down to a JUnit test
already. There is one single JUnit test class. This is This class
has only one test method. 

All this was part of a big application and it took me one hour to distill this one JUnit test.

Please be more precise and tell me what you want or need.

> Side effect when you use QueueBrowser. Missing Message in subsequent calls.
> ---------------------------------------------------------------------------
>                 Key: AMQ-3477
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client, Message Store
>    Affects Versions: 5.4.0, 5.4.1, 5.4.2, 5.5.0
>         Environment: Windows 7 64 Bit
>            Reporter: Klaus Stake
>              Labels: QueueBrowser
>         Attachments: apache-issue.tar.gz
> Since 5.4.0 onwards there seems to be an errorneous side effect, when you use a QueueBrowser.
When you use the QueueBrowser, then the Consumer will miss one Message.
> I use the QueueBrowser to check if Messages are available and for peeking them.
> When I do this and call getConsumer().receive(noWaitTimeOut). Then the first message
in the queue seems to be ignored. I can see this message with the QueueBrowser, but cannot
receive this message anymore.
> I have tried this will all ActiveMQ versions from 4.0.1 up to 5.5.0. The last version
which works for me is 5.3.2.
> Attached you will find a complete Maven project to reproduce this error.
> You must change line 26 in the pom file for changing the ActiveMQ version. The attached
pom uses 5.3.2 which works. When you change the version to some later version, then you will
see a failing unit test.
> -- Klaus

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message