[
https://issues.apache.org/jira/browse/ARTEMIS-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070142#comment-18070142
]
Clebert Suconic commented on ARTEMIS-5982:
------------------------------------------
The order established here:
https://github.com/apache/artemis/blob/007489597b5ac9fb7477b5d29edec8d4184f1a92/artemis-server/src/main/java/org/apache/activemq/artemis/core/remoting/impl/netty/NettyAcceptor.java#L471-L474
is inverted.
I could, for a regular process starting just use the regular order of the
components, however you could have a scenario where the acceptor and the mirror
was added dynamically and you still need to respect the ordering on this case.
(of the lock coordinator being used).
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
