Poison message

Q: How deeply does C# Concurrency: Asynchronous and multithreaded programming cover poison message?

Explains the restart loop and quarantine response, but does not specify retry thresholds or a complete implementation.

As explained in C# Concurrency: Asynchronous and multithreaded programming

A poison message is a message that repeatedly fails processing and may prevent normal queue consumption unless it is isolated or discarded.

A poison message repeatedly crashes or fails processing. With at-least-once delivery, leaving it in the queue can create an endless restart loop: read, fail, restart, and repeat. section 8.2.3

Protect consumption with failure monitoring, such as a try-catch around processing. After repeated failures for the same message, remove it from the main queue and preserve it for inspection. section 8.2.3

Use these safeguards:

Move poison messages to another persistent queue, commonly called a dead letter queue, so the payload and underlying bug can be investigated. section 8.2.3
Prepare or validate messages before enqueueing them so one malformed item does not disrupt an entire operation. section 8.2.3
Account for poison messages when choosing persistent-queue delivery semantics, especially at-least-once delivery. section 8.3

How C# Concurrency: Asynchronous and multithreaded programming covers it

Cover of C# Concurrency: Asynchronous and multithreaded programming

liveBook manning.com

Read C# Concurrency: Asynchronous and multithreaded programming on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Kafka for ArchitectsA poison pill message is a malformed or otherwise unprocessable message that repeatedly causes a consumer or processing stage to fail.

Compare how 2 books explain poison message →

Related concepts

messagekind of · A message is a discrete unit of information or data represented, processed, or exchanged in a communication context.
dead-letter topic patternaddressed by · The dead-letter topic pattern redirects messages that cannot be processed to a separate topic for later investigation or handling.
dead letter queuepart of · A dead-letter queue is a destination that stores messages or records that cannot be delivered or processed normally for later inspection, retry, handling, or disposal.

This explainer was generated by Manning's knowledge graph from the text of C# Concurrency: Asynchronous and multithreaded programming. The section links point to the parts of the book it draws on.