Proactively protecting ActiveMQ from message loss and concurrentStoreAndDispatchQueues on my KahaDB persistent store?
Issue
We would like to enable concurrentStoreAndDispatchQueues to true to ensure that messages are persisted to the database prior to being sent to the consumer. In that way, in case of broker failure, we want to ensure we do not lose any messages. With that being said, are there any other settings that we should be aware of in AMQ and/or with KahaDB that could lead to message loss if not properly addressed?
Environment
- JBoss Fuse 6.X
- JBoss A-MQ 6.X
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.