[ARTEMIS-3501] Corrupted message in journal can inhibit broker from starting

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.19.0
• Assignee: Unassigned
• Reporter: Anton Roskvist
• Created: 28/Sep/21 10:15
• Updated: 30/Sep/21 00:22
• Resolved: 29/Sep/21 18:40

Description

In my case this was caused by a single bad message that seems to have come from a broker restart i.e the broker was working, then it was stopped, and upon starting back up it was unable to do so and instead threw some troubling exceptions in the log (attached)

Issue Links

• links to: GitHub Pull Request #3776