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 2025/08/25 14:35:00 UTC
[jira] [Work logged] (ARTEMIS-5634) Transactions should be used on the server's side when mirror source is in use
[ https://issues.apache.org/jira/browse/ARTEMIS-5634?focusedWorklogId=980274&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-980274 ]
ASF GitHub Bot logged work on ARTEMIS-5634:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Aug/25 14:34
Start Date: 25/Aug/25 14:34
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #5887:
URL: https://github.com/apache/activemq-artemis/pull/5887
if a non transaction send happens while on mirror, the broker should upgrade the operation to an internal transaction to make sure the whole thing happens atomically.
Issue Time Tracking
-------------------
Worklog Id: (was: 980274)
Remaining Estimate: 0h
Time Spent: 10m
> Transactions should be used on the server's side when mirror source is in use
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-5634
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5634
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.42.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.43.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In a rare race, when the producer sends non transactionally, you could have a situation where the MirrorSNF is not sent using the same Transaction. as a Result you could get a situation that you lose part of the routing in that situation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact