[A-MQ, Priority Messages, JDBC store] priority messages seem to be slow when retrieved from JDBC store

Solution Verified - Updated -

Issue

  • since ENTMQ-1064 has been fixed, the broker appears to be slow when using priority messages and JDBC persistent store.

  • This issues only the impacts brokers that contain the fix for ENTMQ-1064, are configured to use priorityMessages=true in the brokers destinations policy and uses JDBC persistence storage.

Environment

  • JBoss A-MQ 6.1 Rollup 2 Patch 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.