🎄 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.

Jms Message Id - default set unique id e. g. GUID if not set by publisher

Robert
Robert Member Posts: 58 ✭✭
edited December 2021 in General Discussions #1

I found that by default use of solace no message id is set when using jms client.
As that field is best to corelate an error on subscriber with message parked in DMQ or perform de-duplication, i wonder if there is a. config in solacd to auto. fill when publisher does not set the ApplicationMessageId which normally turns into JmsMessageId ?

Tagged:

Best Answer

  • amackenzie
    amackenzie Member, Employee Posts: 269 Solace Employee
    #2 Answer ✓

    there is no message ID that gets auto-populated in JMS messages. The PubSub+ JMS provider fully respects ApplicationMessageId when set, even when the message is published by a different API (e.g. published in Java or .Net but consumed via JMS) but your publisher must set it.

Answers

  • amackenzie
    amackenzie Member, Employee Posts: 269 Solace Employee
    #3 Answer ✓

    there is no message ID that gets auto-populated in JMS messages. The PubSub+ JMS provider fully respects ApplicationMessageId when set, even when the message is published by a different API (e.g. published in Java or .Net but consumed via JMS) but your publisher must set it.

  • Robert
    Robert Member Posts: 58 ✭✭
    #4

    @amackenzie Then we must enforce via policies that publisher must set SenderTimeStamp and ApplicationMessageId. I think both fields are quite important and therefore should get set.

Categories

This Month's Leaders

This Week's Leaders