[
https://issues.apache.org/jira/browse/ARTEMIS-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741652#comment-17741652
]
ASF subversion and git services commented on ARTEMIS-4352:
----------------------------------------------------------
Commit 6ee27224a57d3c5ad7b293497d3bfc892a72a8b0 in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=6ee27224a5 ]
ARTEMIS-4352 Avod Deadlock in case the SecurityManager is reusing the Netty
executor.
If the Security Manager is using Netty, and in particular the same Netty
connection,
you could run into a deadlock / starvation.
This is particularly true in the Wildfly case where they reuse the same
connection for everything via XNIO.
> Deadlock can happen during authentication with custom SecurityManager which
> requests the same server
> ----------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-4352
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4352
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.29.0
> Reporter: Emmanuel Hugonnet
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> On session creation the IO thread is blocked during the authentication, this
> may lead to deadlock or starvation.
> The issue is in
> org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler#handlePacket
> which should pass the process to an 'actor'
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
