[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=824597&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-824597
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Nov/22 14:08
Start Date: 09/Nov/22 14:08
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1308820712
@AntonRoskvist it is about the two consecutive rollbacks. One will add a
bunch of data. The second will call the addSorted for a huge list, scanning all
the lists for every rollback item.
If you actually rolled back the consumer's pending first, the adds would be
in order as the addSorted checks for first and last.
I'm adding an optimization to keep the last added position and also check
against the last added, and I will as well have the adds done outside of the
locking.
Issue Time Tracking
-------------------
Worklog Id: (was: 824597)
Time Spent: 3h 20m (was: 3h 10m)
> 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 20m
> 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)
