Incorrect detection of data types in address parameters - C++ client
--------------------------------------------------------------------
Key: QPID-2896
URL: https://issues.apache.org/jira/browse/QPID-2896
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: 0.7
Reporter: Ted Ross
Priority: Critical
Fix For: 0.7
Numeric values in address parameters are incorrectly interpreted as strings.
The following address, run on the c++ client, causes the problem:
my-queue;{create:always,node:{type:queue,x-declare:{arguments:{'qpid.max_count':60}}}}
Reproducer:
$ drain
"my-queue;{create:always,node:{type:queue,x-declare:{arguments:{'qpid.max_count':60}}}}"
$ qpid-config queues
Queue Name Attributes
======================================================================
my-queue Failed: TypeError: %d
format: a number is required, not str
No only does qpid-config misinterpret the value of the 'qpid.max_count' field,
but the broker does as well (i.e. the limit on the queue remains the default).
Note that this works properly when using the Python API. It is an
inconsistency in the way addresses are parsed and encoded with Python doing it
correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
