- Periodically we will have scenarios where there are slow consumers due to bottlenecks in application logic or simply the absence of consumers and would like to prevent a situation where disk utilisation by a specific queue grows to the extent that we exhaust disk space for all other queues.
- We often run into scenarios with a couple of slow consumers, or even a destination with no consumers, in a system with an overall high level of throughput. This causes the entire journal management system to spiral out of control. We need the capability to isolate such journal growth, per destination, such that they have their persistent store directory.
- We would like to confine the runaway journal growth to a specific destination or small number of destinations.
- Red Hat AMQ
- 7.2, 7.1, 7.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.