[
https://issues.apache.org/jira/browse/ARTEMIS-3501?focusedWorklogId=656326&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-656326
]
ASF GitHub Bot logged work on ARTEMIS-3501:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Sep/21 18:28
Start Date: 28/Sep/21 18:28
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on pull request #3776:
URL: https://github.com/apache/activemq-artemis/pull/3776#issuecomment-929515755
At least in my case I end up in #handleNoMessageReferences (from
AbstractJournalStorageManager) and the message is removed by:
storageManager.deleteMessage(msg.getMessageID());
And the following log:
AMQ221019: Deleting unreferenced message id=$MESSAGEID from the journal
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 656326)
Time Spent: 0.5h (was: 20m)
> Corrupted message in journal can inhibit broker from starting
> -------------------------------------------------------------
>
> Key: ARTEMIS-3501
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3501
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Attachments: artemis.log
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
