Re: [qpid c++][NodeJS amqp10] Unexpected message format, got uint at index 1 of headers

2017-03-02 Thread Gordon Sim
On 02/03/17 16:56, Morgan Lindqvist wrote: Hi Matt, Yes, but ttl does not have index 1, I do not understand this. I am missing something. Index 1 is priority, which should be a ubyte. Can you perhaps get a wireshark trace? Or failing that enable trace+:Protocol on the qpid::messaging loggin

Re: [qpid c++][NodeJS amqp10] Unexpected message format, got uint at index 1 of headers

2017-03-02 Thread Morgan Lindqvist
> > 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-ui

Re: [qpid c++][NodeJS amqp10] Unexpected message format, got uint at index 1 of headers

2017-03-02 Thread Matt Broadstone
: 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-form

[qpid c++][NodeJS amqp10] Unexpected message format, got uint at index 1 of headers

2017-03-02 Thread Morgan Lindqvist
. --- header: { durable: false, priority: 4, ttl: , 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