As you are reading the message in a transaction, then rolling back the transaction will send the message to the original queue which will eventually move the message to the DLQ after configured attempts. if you don't want to move the message to DLQ, then the only way which I can see that don't configure the DLQ. The message will be discarded after configured attempts.
On Wed, Jun 21, 2017 at 6:24 PM, adaprior [via ActiveMQ] < ml+s2283324n4727640...@n4.nabble.com> wrote: > Thanks, Vishal. I am not sure how to handle this situation -> I am > currently listening messages from active mq with the transaction and on bad > data in the message body, rollback of DB has to be done but the message > should be sent to a new queue in the same transaction. throwing an > exception sends back the message to DLQ and rollback of DB is done, No > matter how many times this message is sent back to original queue message > will be back to DLQ. > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Artemis- > failure-cause-of-DLQ-messages-tp4726423p4727640.html > To unsubscribe from ActiveMQ Artemis: failure cause of DLQ messages, click > here > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4726423&code=VklTSEFMMzAwN0BHTUFJTC5DT018NDcyNjQyM3w1MjczNTAyOA==> > . > NAML > <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Artemis-failure-cause-of-DLQ-messages-tp4726423p4727721.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
