[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=823977&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-823977
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Nov/22 17:35
Start Date: 07/Nov/22 17:35
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1305958085
They are getting rolled back, that's part of the close() call issued just a
little bit later. (tx.rollback() on line #571 in my change)
The test also makes an assertion on messageCount right at the end.
The previous (much older) behavior was that only XA transactions was handled
here as well:
https://github.com/apache/activemq-artemis/commit/bafefdc8ece23801ac8fb7f5879faa9c3107ae5f
Issue Time Tracking
-------------------
Worklog Id: (was: 823977)
Time Spent: 0.5h (was: 20m)
> 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: 0.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)
