In Hawtio console messages viewed in Queue Browser differ based on changing of prioritizedMessages

Solution Verified - Updated -


  • Why removing messages in queue browser, maxBrowsePageSize is not paged in ?
  • Following is the setup to see the behaviour:

    • Set the "maxBrowsePage=500"
    • Fill queue with 520 messages
    • Action: delete certain messages via operation 'Remove matching messages(java.lang.string)'
    • Expectation: after deleting x messages, the same number of messages is paged in as replacement for the deleted ones, in sum 500 are shown again
  • Testcase 1: messages 1 to 500 are shwon, delete messages 499 and 500 with expression 'JMSXGroupSeq between 499 and 500' (or other criteria matching the last 2 messages paged in) --> confirmation the two messages are deleted, now 501 and 502 are shown/were paged in to fill up to the limit of 500 again --> OK

  • Testcase 2: messages 1 to 500 are shwon, delete messages with 'JMSXGroupSeq between 499 and 501' (that means two message paged/499+500 and one message not paged in/501) --> confirmation the three messages are deleted (499,500,501), but only the two new ones 502 and 503 are shown, but not as expected 504 as the third message --> NOT ok

  • This effect multiplicates with further deletions of messages increasing the gap between maxBrowsePageSize and the number of messages actually displayed, the more you delete the less are shown afterwards.


  • Red Hat JBoss A-MQ
    • 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content