[
https://issues.apache.org/jira/browse/DISPATCH-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619062#comment-14619062
]
ASF subversion and git services commented on DISPATCH-146:
----------------------------------------------------------
Commit 1689926 from [~aconway] in branch 'dispatch/trunk'
[ https://svn.apache.org/r1689926 ]
DISPATCH-146: management query sends non string keys
The management client qdmanage was sending management operation names and some
other
string values as AMQP bytes, causing interop problems. Now sends as AMQP
strings.
> management query sends non string keys
> --------------------------------------
>
> Key: DISPATCH-146
> URL: https://issues.apache.org/jira/browse/DISPATCH-146
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
> Affects Versions: 0.4
> Reporter: Andy Taylor
> Assignee: Alan Conway
> Priority: Minor
> Fix For: 0.5
>
>
> Im not 100% sure this is a bug but when you run a command something like:
> qdmanage query -b url --type linkRoutePattern
> the amqp message contains a map with the entry 'attributeNames' which
> contains an entry where the key is a Binary. The spec says:
> "The body of the message MUST consist of an amqp-value section containing a
> map which MUST have the following entries, where all keys MUST be of type
> string:"
> The reason i found this issue was by running the management client against
> Artemis which produced a class cast exception on the server because of this.
> NB Artemis uses proton-jms to decode messages so if its a not a bug then the
> proton-j decoder will need fixing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
