On 06/10/2015 07:26 PM, logty wrote:
The odd thing is the sender is specifying the delivery-id, here is the output
of PN_TRACE_FRM=1 on the sender side:

[0x86b6580]:0 -> @transfer(20) [handle=0, delivery-id=0,
delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0,
settled=true, more=false] (5243441) "\x00Sp\xd0\x00\x00\x00\x0b\x00\x..."

The delivery tage used by the broker when sending the message out to a consuming client is not (or need not) be the same as the one used by the publishing client.

This is the output from one of the tests, but I can replicate it just using
example programs and inputing large amounts of data, yet even with small
amounts of data the delivery-tag is still not being set when sent to a

Here is the sender:
[0x17471b0]:0 -> @transfer(20) [handle=0, delivery-id=3,
delivery-tag=b"\x03\x00\x00\x00\x00\x00\x00\x00", message-format=0,
settled=false, more=false] (109)

Here is the reciever:
[0x1de3ac0]:0 <- @transfer(20) [handle=0, delivery-id=5, delivery-tag=b"0",

This is ok, that is a 1 byte tage with the ascii value '0' I believe. However the original trace commented on had: delivery-tag=b"", which is a zero byte value.

message-format=0] (122)

View this message in context: 
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.

Reply via email to