[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=823843&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-823843
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Nov/22 09:49
Start Date: 07/Nov/22 09:49
Worklog Time Spent: 10m
Work Description: AntonRoskvist opened a new pull request, #4281:
URL: https://github.com/apache/activemq-artemis/pull/4281
I have observed this happening with far fewer messages and multiple
consumers attached to the same queue, but have been unable to write a
consistent test for it. It also happens with AUTO_ACKNOWLEDGE instead of
transacted sessions but this was easier to implement in a test.
I'm not really happy with the runtime of the test so if anyone has
suggestions on how to make it run faster just let me know.
Issue Time Tracking
-------------------
Worklog Id: (was: 823843)
Remaining Estimate: 0h
Time Spent: 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: 10m
> 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)
