[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=824407&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-824407
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Nov/22 02:17
Start Date: 09/Nov/22 02:17
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1308108324
not a dead lock... it's just the way this rollback happens it is taking a
long time to process. relaxing the locks is the way to go here.
I will see if I can do some optimization.
will be fixed tomorrow :)
it will be after 2.27.0, but we should have a 2.28.0 soon..
Issue Time Tracking
-------------------
Worklog Id: (was: 824407)
Time Spent: 3h (was: 2h 50m)
> Rollbacking massive amounts of messages might crash broker
> ----------------------------------------------------------
>
> Key: ARTEMIS-4084
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4084
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Critical Analyzer triggers, but even if it is set to LOG or disabled the
> broker is put in such a bad state it becomes unresponsive until restarted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
