[A-MQ6, cursorMemoryHighWaterMark ] destination's cursorMemoryHighWaterMark can potentially block message dispatch unexpectedly

Solution Verified - Updated -

Issue

  • by setting a smaller cursorMemoryHighWaterMark on a destination, this may cause the broker to stop loading messages into memory even though there is adequate memory available to load the messages. If messages are not loaded into memory they can not be dispatched to the associated consumers/subscribers.

Environment

  • JBoss A-MQ 6.2.1 GA
  • JBoss A-MQ 6.3 GA

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
Close

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