[
https://issues.apache.org/jira/browse/QPIDJMS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096256#comment-16096256
]
Keith Wall commented on QPIDJMS-305:
------------------------------------
Looking at f5f287e, is seems like {{AmqpSaslAuthenticator}} should no longer
have an {{AsyncResult}} at all. Currently {{AmqpProvider}} gives
{{AmqpSaslAuthenticator}} the AsyncResult through its constructor. It is only
mutated via the {{signalCompletion()}}, which is only by {{AmqpProvider}}.
> Potential race on sasl authentication failures can throw wrong exception on
> connect
> -----------------------------------------------------------------------------------
>
> Key: QPIDJMS-305
> URL: https://issues.apache.org/jira/browse/QPIDJMS-305
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.23.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 0.24.0
>
>
> During the SASL authentication process there's a change that an error thrown
> from the handler code in the exchange phases can result the wrong exception
> being thrown from the connection create methods in the ConnectionFactory due
> to a race between asynchronous notifications and the exception thrown from
> the connect call.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
