[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=824213&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-824213
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Nov/22 13:29
Start Date: 08/Nov/22 13:29
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1307225329
This also happens with Session.AUTO_ACKNOWLEDGE (which is the case where I
first noticed this) though. The reason I use this many messages and a
transaction is because that's the way I could make the test work reliably.
It can also happen with far fewer messages rolled back (but still many) and
with multiple consumers on the same queue.
Issue Time Tracking
-------------------
Worklog Id: (was: 824213)
Time Spent: 1h 40m (was: 1.5h)
> 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: 1h 40m
> 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)
