[
https://issues.apache.org/jira/browse/QPIDJMS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742479#comment-15742479
]
Rob Godfrey commented on QPIDJMS-232:
-------------------------------------
So the new behaviour is strictly superior to the prior behaviour (I didn't
realise that it was opening the TCP/SSL connection and then just waiting - I
presumed that it was deferring the opening of the connection until the client
id was set or other work occurred).
Having a mechanism (on the URL?) to specify that no clientID is being supplied
makes sense... the only potential issue then is with servers that have a
timeout on actually opening the AMQP connection, or those server that
spontaneously send their own open and require heartbeating of their partner.
> Perform Authentication when the remote connection is established instead of
> waiting until Connection is used
> ------------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-232
> URL: https://issues.apache.org/jira/browse/QPIDJMS-232
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.11.1
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 0.20.0
>
>
> Instead of waiting until the connection is used to perform authentication we
> should perform the SASL authentication if available when the connection is
> established. This allows the createConnection methods in the
> ConnectionFactory to fail fast instead of waiting until the Connection is
> used (e.g set client ID, start, createSession etc)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
