liveBook · Manning

Poison message

A poison message is a message that repeatedly fails processing and can prevent normal consumption until it is isolated, rejected, or discarded.

How 2 Manning books explain it

Kafka for Architects

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

How it is used
Frames malformed or incompatible records as an operational failure mode requiring consumer tests, offset recovery, and dead-letter handling.
How deep it goes
Traces failure loops, offset resets, schema incompatibility, and DLT responses, but stops short of implementation walkthroughs.
Examples
Uses missing fields, an added source column, incompatible Avro schemas, connector stoppage, and sink-side DLT redirection.
What you can do after
Diagnose poison messages, reset consumer offsets, configure DLT handling, and monitor connector failures and redirected records.

Read how Kafka for Architects explains poison message →

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.

How it is used
Protects persistent background queues from messages that repeatedly prevent normal consumption.
How deep it goes
Explains the restart loop and quarantine response, but does not specify retry thresholds or a complete implementation.
Examples
Uses a crashing queue item, a try-catch monitor, and a separate persistent queue for failed messages.
What you can do after
Diagnose queue stalls by identifying repeated failures and isolating the offending message for inspection.

Read how C# Concurrency: Asynchronous and multithreaded programming explains poison message →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.