🎄 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.
Reprocessing Messages
I have a scenario similar to the one mentioned in this post
How can I get it to work in JCSMP with spring boot?
Answers
-
Hi @Ali ,
If your consumer is using client acks you want to make sure you either ack or nack each message. This way if a message is nacked it can be redelivered, or sent to a dead message queue (if configured) and max-retries has been reached.
See the Client Acknowledgements section of the docs here: https://docs.solace.com/API/API-Developer-Guide/Acknowledging-Messages.htm
I believe you should be able to set this in your spring properties using:
solace.java.apiProperties.message_ack_mode=JCSMPProperties.SUPPORTED_MESSAGE_ACK_CLIENT
(You will probably have to look up the String value for that enum above...I don't recall)
Hope that helps!
0 -
Hey @marc ,
Thanks for the reply!
I am using client ack mode and the "settle" methods to ack/nack. However, the message never gets redelivered.
I tried breaking the flow by calling close() on the flowReceiver then creating a new flowReceiver, that also did not work. My best guess is that it is using the same session, but creating a new session for every redelivered message may cause performance issues.
Any ideas about what could be happening?
0