[A-MQ, Kahadb] checkForCorruptJournalFiles and ignoreMissingJournalfiles attributes

Solution Verified - Updated -

Issue

According to the Red Hat documentation, when enabled, persistenceAdapter property checkForCorruptJournalFiles will check for corrupted Journal files on startup and try and recover them.
What kind of recovery can take place ? How can data corruption/loss be recovered?

In case of journal corruption (i.e. definitive data loss), we need a way to prevent the broker from starting until some explicit green light is given - e.g. in order to let us the opportunity of restoring a clean archive. What is the procedure/setup to achieve this ?

Environment

Red Hat JBoss A-MQ 6.1.0, 6.2.0

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.