Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Dealing with poison messages in the dead letter queue

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So how can I differentiate the messages in DLQ. because if I reprocess a poison message from DLQ it would again come back to DLQ.
 
author
Posts: 23883
142
jQuery Eclipse IDE Firefox Browser VI Editor C++ Chrome Java Linux Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
BTW... this topic was split off from here ... https://coderanch.com/t/316811/java/JMS-rollback-Dead-Letter

Henry
 
Henry Wong
author
Posts: 23883
142
jQuery Eclipse IDE Firefox Browser VI Editor C++ Chrome Java Linux Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

First of all, this is implementation specific, so, it may help us a bit if you mention which messaging environment you are using.... but ... to answer in a general way...

You really shouldn't be processing messages in the dead letter queue. They are there for a reason, and that is, to be examined to figure out what went wrong. If reprocessing was an option, then you could have achieve the same thing by allowing more redeliveries to consumers.

However, if you really want to process messages in the dead letter queue, then one possible option is to have a different policy for the dead letter queue. Having the policy of the same dead letter queue for the dead letter queue is silly. Perhaps, messages from the dead letter queue, that fail delivery, should be discarded? Or perhaps, it should go to a different queue, as its dead letter queue?

Henry
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic