You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/12/16 10:14:58 UTC
[jira] [Reopened] (QPIDJMS-235) add option to complete AMQP Open
without waiting for a ClientID to [not] be set
[ https://issues.apache.org/jira/browse/QPIDJMS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reopened QPIDJMS-235:
------------------------------------
Assignee: Robbie Gemmell (was: Timothy Bish)
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org