[
https://issues.apache.org/jira/browse/QPIDJMS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095435#comment-16095435
]
ASF subversion and git services commented on QPIDJMS-305:
---------------------------------------------------------
Commit f5f287ec021e2bd881b3992b328c78f48d8397eb in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=f5f287e ]
QPIDJMS-305 Refactor the SASL Authentication process to remove race
Refactor of the SASL Authenticator and the way it handles failures and
how they are then reported. Removes a race where an async provider
exception and the exception returned from the connect call can chase
each other and the wrong one gets tracked as the failure cuase.
> 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: [email protected]
For additional commands, e-mail: [email protected]
