Sai, The images didn't come through on your message, but I have a potential answer based on what you wrote.
I think you're browsing a queue from the web console. Queues are FIFO data structures that provide access to the oldest elements from the head of the queue, so when you consume messages, you'll get the oldest one. Queues in ActiveMQ jave a browse capability, where you can view a small number of the messages at the head of the queue without consuming them, similar to the peek() operation provided by many queue data structure implementations in various programming languages. The size of this batch is small, and based on what you're reporting, it sounds like it's 300 messages. Within this batch, the web console allows you to sort the messages on several properties, so when the pending message count is smaller than the batch size, you can easily view the most recent message even though the queue really provides access to the oldest messages. Once the queue's pending message count exceeds the batch size, this is no longer possible, as you've discovered. If you must have the ability to examine unconsumed messages irrespective of the number of them, you could consider using the JDBC persistence store and connecting it to an external SQL database against which you could do arbitrary queries. But be aware that there are significant tradeoffs associated with the use of the JDBC store type, including the fact that it's slower than KahaDB (I've always understood that throughput was about half that of KahaDB, though I don't have data to support that) and the additional complexity/expense of building, maintaining, and operating a resilient database in addition to the brokers themselves. So consider careful whether the ability to browse arbitrary messages on an arbitrary-length queue is important enough to you to justify those trade-offs. Tim On Sun, Jul 4, 2021, 1:59 AM Chintapanti, Sai <schintapa...@fasttechnology.com.invalid> wrote: > Hi, > > > > We have been using ACTIVE MQ our my project. Recently we observed the if > Queue has more than 300 or 350 records, we could not see latest records > when we sort the timestamp. Could you please help us if we need to change > any settings or config ? > > > > > > > > No latest records showing up > > > > > > Thanks, > > Sai > > > > ------------------------------ > > This email is intended solely for the recipient. It may contain > privileged, proprietary or confidential information or material. If you are > not the intended recipient, please delete this email and any attachments > and notify the sender of the error. >
