Apologies!!! I had a really long day, the behavior is in fact exactly how you
describe it for using the javax.jms.QueueBrowser without a filter. I had a
requirement to both capture the oldest message and message count based on
priority (session.createBrowser(queueName, "JMSPriority = " + priority)
On Thu, Apr 5, 2018 at 5:21 PM, irieb wrote:
> Yeah, sure this is old - but its a top search result when searching for
> this
> problem this reply is wrong, the oldest message when using the queue
> browser is the last one.
You say "the queue browser," which isn't very precise... Are we ta
> ...this reply is wrong, the oldest message when using the queue browser
is the last one.
By "the last one" do you mean the last one that was put in the queue?
Surely the last message put on the queue cannot be older than the messages
that were already in the queue before that message was put the
Yeah, sure this is old - but its a top search result when searching for this
problem this reply is wrong, the oldest message when using the queue
browser is the last one. What makes it worse is when there are over 200
messages, it is the default page size - other than statistics or jolokia i
do
xt:
http://activemq.2283324.n4.nabble.com/Oldest-message-in-queue-tp3007750p3010035.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ldest-message-in-queue-tp3007750p3007750.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
