[
https://issues.apache.org/jira/browse/QPIDJMS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754270#comment-15754270
]
ASF subversion and git services commented on QPIDJMS-235:
---------------------------------------------------------
Commit 84f18152a9b7138c501bf24d9c0089a57accf9b6 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=84f1815 ]
QPIDJMS-235: update documentation to detail new awaitClientID option
> add option to complete AMQP Open without waiting for a ClientID to [not] be
> set
> -------------------------------------------------------------------------------
>
> Key: QPIDJMS-235
> URL: https://issues.apache.org/jira/browse/QPIDJMS-235
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.20.0
>
>
> If no ClientID was configured on the connection URI, the client delays
> sending the AMQP Open frame to allow either for one to be set via
> setClientID, or the Connection to be otherwise used and confirm no ClientID
> can be set. It does this since we use the container-id to carry the ClientID.
> If no ClientID is configured in the URI, and a Connection is created and
> subsequently entirely unused (either via setClientID, or createSession etc)
> for a period, this may delay the Open frame longer than a server will
> tolerate.
> We should add an option to provoke the AMQP connection to be Opened
> immediately to allow for connections without a ClientID to succeed in this
> scenario.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
