qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-56) throw InvalidClientIDException rather than JMSException when hint present that container-id was the problem field
Date Fri, 29 May 2015 14:39:18 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564902#comment-14564902
] 

ASF subversion and git services commented on QPIDJMS-56:
--------------------------------------------------------

Commit cfb65ee616ef4f4d3e0ce36c93c5d4dd8800940c in qpid-jms's branch refs/heads/master from
Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=cfb65ee ]

QPIDJMS-56: move test alongside the matching 'no-hint' test


> 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


Mime
View raw message