[
https://issues.apache.org/jira/browse/ARTEMIS-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028602#comment-18028602
]
ASF subversion and git services commented on ARTEMIS-5697:
----------------------------------------------------------
Commit 31bad3fd1ffea45f712321ecdb6dd418a6bb9356 in activemq-artemis's branch
refs/heads/main from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=31bad3fd1f ]
ARTEMIS-5697 Close down the proton transport on sasl client failures
When the SASL failure occurs from an outgoing broker connection attempt close
down the transport and detach from the SASL client listener to avoid a loop.
> 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: 20m
> 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: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
