[
https://issues.apache.org/jira/browse/QPIDJMS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742291#comment-15742291
]
Rob Godfrey commented on QPIDJMS-232:
-------------------------------------
Purely out of curiosity - if you are allowing the client Id to be set "later"
is the plan here that you will do SASL negotiation (if any) / TLS handshake (if
applicable) then wait before sending the open frame?
This sort of behaviour may give rise to timeout exceptions on servers that
expect the connect - authenticate - open sequence to happen in quick succession
(the Qpid Java Broker for instance has some timeouts in place here) certainly
it seems possible that you'll run into issues where one side is expecting
heartbeating. As such it would seem prudent to make this behaviour
configurable.
> Perform Authentication when the remote connection is established instead of
> waiting until Connection start
> ----------------------------------------------------------------------------------------------------------
>
> 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 started 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
> later started or a client ID is set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
