exception - 配置了 maxRedeliveryAttempts 和 VM 入站的回滚策略不会重新传送消息

Question

我的流程如下所示，我希望消息被重新传递 2 次，然后

Redelivery is exhaused SAD

要打印的记录器。但是组件抛出异常后，重新传递机制并没有启动

<vm:connector name="VM" validateConnections="true" doc:name="VM" />


<flow name="TriggerFlow" >
    <http:listener config-ref="Orders_HTTP_Listener_Configuration" path="/rollback" allowedMethods="GET" doc:name="1080/rollback" />
    <vm:outbound-endpoint exchange-pattern="request-response" path="txFlow" doc:name="VM" connector-ref="VM" responseTimeout="60000">                      
    </vm:outbound-endpoint>
</flow>

<flow name="TxFlow" >
    <vm:inbound-endpoint exchange-pattern="request-response" path="txFlow" doc:name="case1" connector-ref="VM" responseTimeout="60000">
        <xa-transaction action="ALWAYS_BEGIN"/>
    </vm:inbound-endpoint>
    <scripting:component doc:name="Groovy">
        <scripting:script engine="Groovy"><![CDATA[throw new RuntimeException();]]></scripting:script>
    </scripting:component>
    <rollback-exception-strategy maxRedeliveryAttempts="3" doc:name="Rollback Exception Strategy">
        <logger message="Will rollback #[payload]" level="INFO" doc:name="Logger"/>
        <on-redelivery-attempts-exceeded>
            <logger message="Redelivery is exhaused SAD " level="INFO" doc:name="Logger"/>
        </on-redelivery-attempts-exceeded>
    </rollback-exception-strategy>
</flow>

Answer 1

在与 MuleSoft 交谈后，我终于得到了答案。更新后的流程应如下所示，VM 应该是单向的，并且 TxFlow 的处理策略应该是同步的。如果虚拟机是请求响应式的，那么它的行为更像是一个流引用，不涉及队列，因此不需要重新传递...