[QUERY] JMS destination for dead letter queue of a topic subscription

[ajuhasz88]

Query/Question
Hi all, can anyone please tell me what JMS destination could be used to access the dead letter queue? Using a premium tier service bus via Spring and JMS.

Why is this not a Bug or a feature Request?
JMS is supported on premium tier and application level dead lettering is a topic covered by the official docs, albeit only with .NET examples.

Setup (please complete the following information if applicable):

• OS: [e.g. iOS]
• IDE: [e.g. IntelliJ]
• Library/Libraries: Spring Boot 3.3 via the JMS 2.0 API

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Query Added
• Setup information Added

[github-actions]

@moarychan @Netyyyy @rujche @saragluna

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[saragluna]

Hi @ajuhasz88, if your question is how to send message to a dlq, then you could achieve this by setting a property on the JMS message:

msg.setIntProperty(JmsMessageSupport.JMS_AMQP_ACK_TYPE, ackType);

For the ackType, we can use the REJECTED, which maps to Service Bus deadletter, as you could see from this doc.

If you want to receive messages from the dlq, then the name would be like some-queue/$deadletter or some-subs/$deadletter. As you could see from this doc.

[ajuhasz88]

Hi @ajuhasz88, if your question is how to send message to a dlq, then you could achieve this by setting a property on the JMS message:

msg.setIntProperty(JmsMessageSupport.JMS_AMQP_ACK_TYPE, ackType);
For the ackType, we can use the REJECTED, which maps to Service Bus deadletter, as you could see from this doc.

If you want to receive messages from the dlq, then the name would be like some-queue/$deadletter or some-subs/$deadletter. As you could see from this doc.

Thanks!
I assume then we must use CLIENT_ACK as the acknowledge mode for this to work, right?

However this rules out session transacted connections on the receiver side, is there no explicit JMS destination support for the DLQ? Is there any way to have session transacted connection as well as do application driven DLQing?