[
https://issues.apache.org/jira/browse/QPID-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated QPID-6330:
------------------------------
Summary: [C++ Messaging] Server example differences using 0-10 vs 1.0
protocol (was: [C++ Messaging] Server example differrences using 0-10 vs 1.0
protocol)
> [C++ Messaging] Server example differences using 0-10 vs 1.0 protocol
> ---------------------------------------------------------------------
>
> Key: QPID-6330
> URL: https://issues.apache.org/jira/browse/QPID-6330
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.30
> Environment: Qpidd trunk broker
> Qpid trunk server runs 0-10 or 1.0 protocol
> Amqp.Net Lite interop client
> Reporter: Chuck Rolke
> Attachments: qpid-6330-client-sends-uint.patch
>
>
> Depending on which protocol the server uses it receives different data types
> from the broker. The test setup is:
> * The client program sends messages with Amqp Values of various types.
> * The messaging server program is modified to include the received data type
> and content encoding in the generated reply.
> Running the client twice but having the server use amqp1.0 and amqp0-10
> generates these server logs:
> {noformat}
> > ./server localhost:5672 "{protocol:amqp1.0}"
> Pr: True -> VAR_BOOL True
> Pr: False -> VAR_BOOL False
> Pr: 11 -> VAR_UINT8 11
> Pr: 2222 -> VAR_UINT16 2222
> Pr: 333333333 -> VAR_UINT32 333333333
> Pr: 4444444444444444 -> VAR_UINT64 4444444444444444
> Pr: -11 -> VAR_INT8 -11
> Pr: -2222 -> VAR_INT16 -2222
> Pr: -44444444 -> VAR_INT32 -44444444
> Pr: -8888888888888888 -> VAR_INT64 -8888888888888888
> Pr: 1225568100000 -> VAR_INT64 1225568100000
> Pr: -88.8799973 -> VAR_FLOAT -88.8799973
> Pr: 111111111111111.22 -> VAR_DOUBLE 111111111111111.22
> Pr: f275ea5e-0c57-4ad7-b11a-b20c563d3b71 -> VAR_UUID
> f275ea5e-0c57-4ad7-b11a-b20c563d3b71
> Pr: amqp -> VAR_STRING UTF8 AMQP
> Pr: [True, False, 11, 2222, 333333333, 4444444444444444] -> VAR_LIST [True,
> False, 11, 2222, 333333333, 4444444444444444]
> Pr: {boolFalse:False, boolTrue:True, ubyte:11} -> VAR_MAP {boolFalse:False,
> boolTrue:True, ubyte:11}
> > ./server localhost:5672
> Pr: [True] -> VAR_LIST [True]
> Pr: [False] -> VAR_LIST [False]
> Pr: [11] -> VAR_LIST [11]
> Pr: [2222] -> VAR_LIST [2222]
> Pr: [333333333] -> VAR_LIST [333333333]
> Pr: [4444444444444444] -> VAR_LIST [4444444444444444]
> Pr: [-11] -> VAR_LIST [-11]
> Pr: [-2222] -> VAR_LIST [-2222]
> Pr: [-44444444] -> VAR_LIST [-44444444]
> Pr: [-8888888888888888] -> VAR_LIST [-8888888888888888]
> Pr: [1225568100000] -> VAR_LIST [1225568100000]
> Pr: [-88.8799973] -> VAR_LIST [-88.8799973]
> Pr: [111111111111111.22] -> VAR_LIST [111111111111111.22]
> Pr: �u�^
> WJױ�
> V=;q -> VAR_STRING BINARY �U�^
> WJױ�
> V=;Q
> Pr: amqp -> VAR_STRING UTF8 AMQP
> Pr: [True, False, 11, 2222, 333333333, 4444444444444444] -> VAR_LIST [True,
> False, 11, 2222, 333333333, 4444444444444444]
> Pr: {boolFalse:False, boolTrue:True, ubyte:11} -> VAR_MAP {boolFalse:False,
> boolTrue:True, ubyte:11}
> {noformat}
> The amqp1.0 version produces the expected input and output from the server.
> Running amqp0-10 the server receives VAR_LIST data types where it should be
> receiving other data types.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
