You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/05/28 13:27:18 UTC
[jira] [Commented] (QPIDJMS-56) throw InvalidClientIDException
rather than JMSException when hint present that container-id was the
problem field
[ https://issues.apache.org/jira/browse/QPIDJMS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562703#comment-14562703 ]
ASF subversion and git services commented on QPIDJMS-56:
--------------------------------------------------------
Commit 7e1325e9afae349b9a474ddcb33c8b7bbc1bbbd6 in qpid-jms's branch refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=7e1325e ]
QPIDJMS-56: throw InvalidClientIDException dueing connection failure when hint is present that the container-id field was the problem
Changes by Tim and I.
> throw InvalidClientIDException rather than JMSException when hint present that container-id was the problem field
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-56
> URL: https://issues.apache.org/jira/browse/QPIDJMS-56
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.2.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.3.0
>
>
> For the JMS Mapping we are using container-id to carry the clientid, with a capabilities mechanism to request sole use. When the broker rejects a connection because the clientid is already in use, it does this with an 'amqp:invalid-field' error condition and descriptive message. In order to let the client know which field is specifically considered invalid we discussed adding a generic hint to the error 'info' fields map to allow indicating this, thus allowing use of the mechanism for any field during in other types of connection rejection. We decided upon ncluding a symbol key "invalid-field" mapped to the name of the field in the Open frame that was considered invalid, in this case "container-id".
> When this hint is present for the container-id field of the Open frame during a connection failure, the client should throw InvalidClientIDException rather than a generic JMSException as has previously.
--
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