[
https://issues.apache.org/jira/browse/ARTEMIS-4084?focusedWorklogId=824235&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-824235
]
ASF GitHub Bot logged work on ARTEMIS-4084:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Nov/22 15:03
Start Date: 08/Nov/22 15:03
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4281:
URL:
https://github.com/apache/activemq-artemis/pull/4281#issuecomment-1307359141
@clebertsuconic when this happened with Session.AUTO_ACKNOWLEDGE there where
10 consumers running with 5 or 10MB as limit for consumerWindowsSize. The
consuming application ran into issues with it's own resources so processing
slowed down significantly (so all consumer buffers filled up), then the
application either crashed or where killed, not sure which, but the result on
the broker side was this.
I suppose if the test passes it might be load related, I only tried this out
on a... "not super performant laptop". Could you possibly try increasing the
messageCount?
I also just realized... in my test case there is only a single transacted
session, why is the rollback issued twice (with one very large and then a quite
small batch)? I suppose that might put high pressure on the
"org.apache.activemq.artemis.utils.collections.LinkedListImpl.addSorted()" if
the large batch arrives in order and then the smaller batch does not, such that
the entire list has to be checked for every message in batch 2?
Issue Time Tracking
-------------------
Worklog Id: (was: 824235)
Time Spent: 2h 10m (was: 2h)
> 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 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)
