[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=823968&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-823968
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Nov/22 17:02
Start Date: 07/Nov/22 17:02
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1305913524
I don't think this fix is valid as it's changing the semantics of the
transaction rollback when a session fails. Previously _any_ pending transaction
was rolled back whether or not it has a xid. Now you're only rolling back
transactions with a xid which means in your test the transactions aren't being
rolled back at all. It's perfectly valid for a transaction not to have a xid
and such transactions should be rolled back when a session fails.
Issue Time Tracking
-------------------
Worklog Id: (was: 823968)
Time Spent: 20m (was: 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: 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)
