Broker starts even if corrupted live journal data is detected
Issue
It would appear the broker starts even if corrupted live journal data is detected.
This is a major concern to us as the broker must never start if it detects corrupted live Journal data. This would be disastrous if normal business processing is run based on past corrupted data.
Environment
- Red Hat JBoss A-MQ 6.2.0
- Corrupt journal data
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
