Moving messages from deadletter queue to main queue in Solace

General Discussions
5

@Poornima, have you considered using HermesJMS? I believe it has the ability to move messages between queues.

There are a couple of points to consider here:

  1. The broker doesn’t allow PubSub+ Manager to access message contents. Doing so would violate a security principle: admin users administer the broker, NOT the message data.
  2. As @marc pointed out, moving messages from a DMQ to another queue should not be automated. If a message is on a DMQ, it’s the messaging architecture’s way of saying “something is really broken here. I need you to help fix it!”

Some examples of where moving a message from a DMQ to a normal queue makes sense:

  1. The contents of the message broke the consumer (caused it to crash) - the so called poison message case. You’ve updated the consumer to handle the poison message, deployed the new code and now you need to process the previously poison messages. There is no order dependency in the messages;
  2. Your consumer was temporarily over loaded and messages were not processed in time and so expired to the DMQ. You’ve scaled up the consumer to deal with this load in future, validated that the messages still need to be processed, and know that there is no order dependency.

Some examples of where moving a message from a DMQ to a normal queue should not happen:

  1. The messages need to be processed in order;
  2. Your consumer didn’t know what to do with the message so just didn’t acknowledge it;
  3. The DMQ is being used for business logic exception processing.

I hope that helps!