🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

How to retain original message properties like topic and sender ID when a message is moved to a DMQ

sjaak
sjaak Member Posts: 109 ✭✭✭
edited August 2021 in PubSub+ Event Broker #1

Hi,
We are using Solace properties to dynamically route messages in Boomi on the Boomi listener side. For example sender ID or topic.

However, if a message is moved to a DMQ after x retries, these properties are gone. My question is: is it possible to retain these properties? What happens now is that, after we moved the messages to the original queue, the Boomi process will fail/behaves differently.

Tagged:

Best Answer

  • sjaak
    sjaak Member Posts: 109 ✭✭✭
    edited August 2021 #2 Answer ✓

    It looks like JMSToolbox is changing the Solace header properties! We did some testing with Boomi and Boomi does not touch them.

    But this means we have an operational issue. Customers are using JMSToolbox to move messages from Queue A to B. Reason: the Solace Cloud UI does not support this.

    Sorry to ask this again but when will Solace add functionality to the Solace Cloud UI to enable basic features like this?

Answers

  • sjaak
    sjaak Member Posts: 109 ✭✭✭
    edited August 2021 #3 Answer ✓

    It looks like JMSToolbox is changing the Solace header properties! We did some testing with Boomi and Boomi does not touch them.

    But this means we have an operational issue. Customers are using JMSToolbox to move messages from Queue A to B. Reason: the Solace Cloud UI does not support this.

    Sorry to ask this again but when will Solace add functionality to the Solace Cloud UI to enable basic features like this?

  • Robert
    Robert Member Posts: 58 ✭✭
    #4

    @sjaak Which properties are you talking about ?

    I only found one problem with JmsToolbox and that is not the fault of the Toolbox but of what happens inside Solace and that is the switch of DMQEligible Flag which is in main queue set to: True in DMQ to false. That means a copy back from DMQ via JMSToolbox raises a risk if error still persists of message loss as instead to move again to DMQ the messages would be discarded.

    So if you find any changes of properties i would be interested which ones you detected and please check if the values get really changed by JMSToolbox or maybe by move from main queue to DMQ.

    It makes a big difference to see where the real problems comes from.

  • Robert
    Robert Member Posts: 58 ✭✭
    #5

    If you mean and that it sounds the delivery-count from normal retry is maybe removed as well when messages are moved to DMQ then again a problem of solace implementation and not the JMSToolbox tool. :-) But please bring more light into your findings.

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #6

    I'm guessing he's talking about the Destination, probably switching from a Topic in the original published message to a Queue, since JMSToolbox is publishing (not moving) a copy of the message to a specific queue. If published on a Topic again, it would goto all other queues that are subscribed to that.

    Note that the broker has a copy message feature now that retains all original header/metadata values, so hopefully JMSToolbox isn't needed for that use case.

Categories

This Month's Leaders

This Week's Leaders