ActiveMQ Memory still increasing after setting cursorHighWatermark
Issue
We have a situation where we need to be able to store millions of persistant messages, on disk, even during times where there are no consumers.
We are unable to use producer flow control since this message broker, in a BCP situation, needs to hold 24 hrs worth of messages.
At the rate the memory is increasing we will easily hit 100% memory use in just a few hours. We have plenty of disk space; we need a way to have AMQ stop writing to memory in s situation where messages start to build and there are no consumers.
Environment
Fuse Message Broker 7.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
