[
https://issues.apache.org/jira/browse/DISPATCH-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617112#comment-14617112
]
Ted Ross commented on DISPATCH-146:
-----------------------------------
More detail:
Using the command:
{noformat}
PN_TRACE_FRM=1 qdmanage query --type linkRoutePattern
{noformat}
The following message is sent by qdmanage:
{noformat}
\x00Sp\xd0 \x00\x00\x00\x0b \x00\x00\x00\x05
BP\x04@BR\x00
\x00Ss\xd0 \x00\x00\x00J\x00\x00\x00\x0d
@@@@
\xa1&amqp:/_topo/0/Router.A/temp.juQY2pW8HqS\x01
@@\x83\x00\x00\x00\x00\x00\x00\x00\x00
\x83\x00\x00\x00\x00\x00\x00\x00\x00
@R\x00@
\x00S\x74\xd1 \x00\x00\x00[ \x00\x00\x00\x08
\xa1\x09operation
\xa0\x05QUERY <-----
\xa1\x0aentityType
\xa0\x10linkRoutePattern <----
\xa1\x04type
\xa0\x13org.amqp.management <----
\xa1\x04name
\xa0\x04self <----
\x00Sw\xd1\x00\x00\x00\x1d\x00\x00\x00\x02\xa0\x0eattributeNames\xd0\x00\x00\x00\x04\x00\x00\x00\x00
{noformat}
Note the \xa0 (vbin8) encodings of the value strings in the
ApplicationProperties (highlighted by arrows). It's likely that this is
causing the problem reported.
Please note that this is not in violation of the quoted standard text above
since the keys are encoded as strings (\xa1). These values should, however, be
encoded as 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]
