Home/ Questions/Q 7721081
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T03:50:02+00:00

<flow name=RollbackFlow> <jms:inbound-endpoint queue=QIN> <jms:transaction action=ALWAYS_BEGIN/> </jms:inbound-endpoint> <component class=TestComponent/> <default-exception-strategy> <rollback-transaction exception-pattern=*/> </default-exception-strategy> </flow>

  • 0
<flow name="RollbackFlow">
    <jms:inbound-endpoint queue="QIN">
        <jms:transaction action="ALWAYS_BEGIN"/>
    </jms:inbound-endpoint>
    <component class="TestComponent"/>
    <default-exception-strategy>
       <rollback-transaction exception-pattern="*"/>
    </default-exception-strategy>
</flow>

In this flow when an exception is thrown by the Test component, the message is dequeued from QIN. How do I modify the flow so that message will not get dequeued from QIN?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Rollback is the default behavior, this part of the config is redundant. Next, I’m not sure what you’re seeing is dequeing, otherwise the whole promise of transactions in Mule would be dysfunctional. Probably one of these 2 things are happening:

    1. ActiveMQ’s prefetch policy – the message is not immediately put back on the queue, try waiting for a while.
    2. It gets resubmitted immediately after a rollback too many times and ends up in the dead-letter queue (DLQ) – check with AMQ web console.

    Andrew

    • 0