On Thu, Mar 2, 2017 at 11:35 AM, Morgan Lindqvist
<morgan.lindqv...@ericsson.com> wrote:
> Hi All,
>
> I am using the Node JS library amqp10 (ver 3.2.5) together with quid c++
> (ver 1.35).
>
> I just started defining the TTL parameter in the header and now quid c++
> give me the following warning.
>
> ---
> [Unspecified] warning Unexpected message format, got uint at index 1 of
> headers
> ---
>
> The TTL functionality looks like it is working, setting to a small value
> results in that the message is dropped.
>
> I however do not like warnings in the logs if they can be avoided. Is this a
> feature or a bug or misses of the libraries?
>
> If I in Node JS log the header part I get the following output.
> ---
> header:
> { durable: false,
> priority: 4,
> ttl: 9999,
> firstAcquirer: true,
> deliveryCount: undefined },
> ---
>
> Proposals on how to fix this is appreciated.
>
> /Morgan
>
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/qpid-c-NodeJS-amqp10-Unexpected-message-format-got-uint-at-index-1-of-headers-tp7659927.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
Hi Morgan,
This looks like it might be a bug in qpid, as this field is defined as follows:
<field name="ttl" type="milliseconds"/>
Where milliseconds are define as:
<type name="milliseconds" class="restricted" source="uint"/>
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
