You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/04/08 15:15:00 UTC
[jira] [Work logged] (ARTEMIS-4207) Redistribution may leave large messages stranded
[ https://issues.apache.org/jira/browse/ARTEMIS-4207?focusedWorklogId=855611&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-855611 ]
ASF GitHub Bot logged work on ARTEMIS-4207:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Apr/23 15:14
Start Date: 08/Apr/23 15:14
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4432:
URL: https://github.com/apache/activemq-artemis/pull/4432#issuecomment-1500911579
This is just avoiding creating a TransactionImpl object if no route is going to happen.
Issue Time Tracking
-------------------
Worklog Id: (was: 855611)
Time Spent: 1h 20m (was: 1h 10m)
> Redistribution may leave large messages stranded
> ------------------------------------------------
>
> Key: ARTEMIS-4207
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4207
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.28.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.29.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> If you are redistributing messages, eventually between the copy of the large message and the actual call to redistribute the routing table may change, leaving a message behind.
> I could see this happening more oftenly on a test where I had 2 tests in clustered, and one server was shutdown with Ctrl-C (SIGINT) rather than kill -9.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)