<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Rabbitmq on 1Stop</title><link>https://blogs.rameskum.com/tags/rabbitmq/</link><description>Recent content in Rabbitmq on 1Stop</description><image><title>1Stop</title><url>https://blogs.rameskum.com/images/og-default.png</url><link>https://blogs.rameskum.com/images/og-default.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Oct 2026 21:00:00 +0530</lastBuildDate><atom:link href="https://blogs.rameskum.com/tags/rabbitmq/index.xml" rel="self" type="application/rss+xml"/><item><title>Dead Letter Queues: Where Your Poison Messages Actually Go</title><link>https://blogs.rameskum.com/posts/dead-letter-queues-poison-messages/</link><pubDate>Wed, 14 Oct 2026 21:00:00 +0530</pubDate><guid>https://blogs.rameskum.com/posts/dead-letter-queues-poison-messages/</guid><description>One malformed message, retried forever, blocking everything behind it. Dead letter queues are where poison messages go to stop hurting you — with backoff, attempt limits, and alerts. Spring Kafka @DltHandler, RabbitMQ DLX, and the two 2026 broker gotchas that break poison handling silently.</description></item></channel></rss>