You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/04/01 13:18:00 UTC
[jira] [Commented] (ARTEMIS-5982) The lock coordinator should start the acceptor last, not first
[ https://issues.apache.org/jira/browse/ARTEMIS-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070334#comment-18070334 ]
ASF subversion and git services commented on ARTEMIS-5982:
----------------------------------------------------------
Commit 48da8546b45dd8cd49c166e248f06f09face17a3 in artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=48da8546b4 ]
ARTEMIS-5982 Fix start Ordering between Acceptor and Mirroring
> The lock coordinator should start the acceptor last, not first
> --------------------------------------------------------------
>
> Key: ARTEMIS-5982
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5982
> Project: Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I implemented ordering on the lock coordinator to avoid a situation where a message.send could not be captured between the acceptor start and the mirror start. I got the order inverted and this is fixing that issue.
> There's a small window (of milliseconds or even less) that if a message arrives before the mirror is started you could miss the event.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org