Accessing x-death header data from c# client

[Stephen Swensen]

Hello,

Is it possible to access the x-death header from the RabbitMQ C# client? Using the EventingBasicConsumer, the BasicDeliveryEventArgs available when receiving a message doesn't appear to provide access to the x-death count value for example. There is BasicDeliveryEventArgs.Redelivery that tells you if the message is at least once redelivered, and there is BasicDeliveryEventArgs.Headers but it only appears to contain custom headers.

Thanks!

Stephen

[Michael Klishin]

See http://rabbitmq.github.io/rabbitmq-dotnet-client/api/RabbitMQ.Client.IBasicProperties.html#RabbitMQ_Client_IBasicProperties_Headers.

Message properties include a map of headers, and x-death is a key in that map.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Stephen Swensen]

Thanks for response, Michael -

I tried looking in BasicDeliveryEventArgs.BasicProperties.Headers but it doesn't contain the x-death key - it appears to only contain custom headers I set when publishing a message.

On Wednesday, February 14, 2018 at 12:13:20 PM UTC-5, Michael Klishin wrote:

See http://rabbitmq.github.io/rabbitmq-dotnet-client/api/RabbitMQ.Client.IBasicProperties.html#RabbitMQ_Client_IBasicProperties_Headers.

Message properties include a map of headers, and x-death is a key in that map.

On Wed, Feb 14, 2018 at 3:03 PM, Stephen Swensen <stephen...@gmail.com> wrote:

Hello,

Is it possible to access the x-death header from the RabbitMQ C# client? Using the EventingBasicConsumer, the BasicDeliveryEventArgs available when receiving a message doesn't appear to provide access to the x-death count value for example. There is BasicDeliveryEventArgs.Redelivery that tells you if the message is at least once redelivered, and there is BasicDeliveryEventArgs.Headers but it only appears to contain custom headers.

Thanks!

Stephen

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michael Klishin]

That likely means the message was never expired. You can inspect what's being
sent on the wire with Wireshark:
http://www.rabbitmq.com/amqp-wireshark.html.

[Stephen Swensen]

I figured out my misunderstanding: I was doing a BasicNack with requeue=true and expecting the x-death header to be set, however that header doesn't get set unless / until we do a BasicNack with requeue=false and the message is actually dead-lettered.

Thanks for a helpful hand!

Stephen

[Michael Klishin]

Ah, good point. Thank you for reporting back to the list!

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.