[
https://issues.apache.org/jira/browse/ARTEMIS-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-4352:
------------------------------------
Summary: Deadlock can happen during authentication with custom
SecurityManager which requests the same server (was: Deadlock can happen
during JMS authentication with custom realm which requests the same server)
> 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: 10m
> 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)
