You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2025/10/13 15:46:00 UTC
[jira] [Closed] (ARTEMIS-5697) Fix looping call from AMQP Sasl handling on no available mechanisms
[ https://issues.apache.org/jira/browse/ARTEMIS-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clebert Suconic closed ARTEMIS-5697.
------------------------------------
> Fix looping call from AMQP Sasl handling on no available mechanisms
> -------------------------------------------------------------------
>
> Key: ARTEMIS-5697
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5697
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.42.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.43.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Occasionally the below test fails or hangs while the broker handles the case that not mechanisms are available between the two peers and it stages a close on the outgoing connection from the broker connection. The handler needs to close down the proton transport and stop listening to the SASL client events channel so that loop isn't created while processing the and pumping the transport events.
> {code:java}
> org.apache.activemq.artemis.tests.integration.amqp.connect.AMQPConnectSaslTest#testConnectionFailsIfFilterExcudesAnyOfferedMechanism{code}
--
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