[
https://issues.apache.org/jira/browse/ARTEMIS-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640082#comment-17640082
]
ASF subversion and git services commented on ARTEMIS-4084:
----------------------------------------------------------
Commit 66da97a3b151cfbf0f81fb32abda953b361b7170 in activemq-artemis's branch
refs/heads/2.27.x from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=66da97a3b1 ]
ARTEMIS-4084 Fixing addSorted with large transactions
when cancelling a large number of messages, the addSorted could be holding a
lock for too long causing the server to crash under CriticalAnalyzer
co-authored: AntonRoskvist <[email protected]> (discovering the issue
and providing the test ClientCrashMassiveRollbackTest.java)
(cherry picked from commit 03b82142eb0844b9de02ca3d7ed365d849e3ac02)
> 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
> Affects Versions: 2.26.0, 2.27.0
> Reporter: Anton Roskvist
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.28.0
>
> Time Spent: 5h
> 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)
