[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=824356&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-824356
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Nov/22 21:47
Start Date: 08/Nov/22 21:47
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1307870524
@AntonRoskvist the issue is not on the transactions itself. Your rollback
ordering here is uncovering some bug on LinkedListImpl::addSorted. For some
reason this will only happen if you used the Core API. Some sort of duplicate
adds is probably causing it, because if I simply used a regular
ConnectionFActory it worked fine.
if you go to LInkedListImpl::addSorted, there is something in a loop after
the rollback.
The CriticalAnalyzer actually killed your broker correctly on this case...
as the logic was lost.
I will need to work on it tomorrow... but if you could also take a look on
that?
Issue Time Tracking
-------------------
Worklog Id: (was: 824356)
Time Spent: 2h 40m (was: 2.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: 2h 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)
