[
https://issues.apache.org/jira/browse/QPIDJMS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096394#comment-16096394
]
ASF subversion and git services commented on QPIDJMS-305:
---------------------------------------------------------
Commit 62e30c0fc254a2a832b81c3c9a8cf5332ddf9cf5 in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=62e30c0 ]
QPIDJMS-305 Remove the request object from the authenticator
Remove the request object from the authenticator and let the provider
just manage calls to success and failure since it drives the
notification now.
> 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
