Hello,
I've figured it out : if ActiveMQ receives a NACK frame (or if it
doesn't receive an ACK frame while it expects it) then by default it
sends the message to the DLQ (provided that the message has persistent
delivery.)
How can I correct the documentation?
Regards,
Aimée Quinaou
Le 07/06/2019 à 18:06, Aimee Quinaou a écrit :
Hello,
I've read in the FAQ, under "How do I unack the message with STOMP",
that "There is no explicit “unack” command in Stomp"
(http://activemq.apache.org/how-do-i-unack-the-message-with-stomp).
It was true for the first version of STOMP, but since STOMP 1.1
there's a NACK frame that can be used to tell the server that the
client did not consume the message.
(https://stomp.github.io/stomp-specification-1.1.html#NACK)
Now ActiveMQ uses STOMP 1.1 (at least in ActiveMQ version 5.15.9), so
this page is outdated. I suggest that it tells for which versions of
ActiveMQ it is still accurate.
I'm using a python client to consume messages from ActiveMQ, using the
STOMP protocol. If something goes wrong while processing the message I
send a NACK frame, else I send an ACK frame.
I would like ActiveMQ to put the message in the DLQ if it receives a
NACK. How can I do that?
Thanks.
Regards,
Aimée Quinaou
--
*Aimée Quinaou
Développeuse Coopener*
544/09 74 19 26 02
*Cet email a été envoyé grâce à de l'électricité 100% renouvelable et
coopérative !*
