Skip to content

Conversation

cshannon
Copy link
Contributor

@cshannon cshannon commented Jul 6, 2015

A QueueBrowser no longer checks expiry on messages to prevent a
browser from hanging in between the hasMoreElements check and actually
getting a message. This means that if messages were in the queue when
the browser started it will receive messages even if they are now
expired. Even though the browser will get the expired message, the
broker will still expire it to prevent future access to it.

A QueueBrowser no longer checks expiry on messages to prevent a
browser from hanging in between the hasMoreElements check and actually
getting a message.  This means that if messages were in the queue when
the browser started it will receive messages even if they are now
expired. Even though the browser will get the expired message, the
broker will still expire it to prevent future access to it.

Thanks to Henno Vermeulen for providing a test case.
@asfbot
Copy link

asfbot commented Jul 6, 2015

ActiveMQ-PR-Build #83 SUCCESS
This pull request looks good

@asfgit asfgit closed this in 3ba28f6 Jul 6, 2015
@cshannon cshannon deleted the AMQ-5340 branch August 1, 2017 11:01
cesarhernandezgt added a commit to cesarhernandezgt/activemq that referenced this pull request Jun 2, 2025
…T.x-patch

Update to Jetty 9.4.57.v20241219 and improved release notes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants