Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.0.1
-
Fix Version/s: Tech. Debt
-
Component/s: Core: Routing / Filters
-
Labels:None
-
User impact:High
-
Similar Issues:None
Description
Messages being stopped hby the idempotent-receiver-router aren't processed by the forwarding-catch-all-strategy. For instance, in the following config:
<inbound>
<jms:inbound-endpoint queue="orders">
<message-properties-transformer scope="outbound">
<add-message-property key="orderId" value="#[header:INBOUND:orderId]"/>
</message-properties-transformer>
</jms:inbound-endpoint>
<idempotent-receiver-router idExpression="#[header:OUTBOUND:orderId]"/>
<forwarding-catch-all-strategy>
<vm:outbound-endpoint path="duplicate.orders" exchange-pattern="one-way"/>
</forwarding-catch-all-strategy>
</inbound>
A duplicate message is caught by the idempotent-receiver-router but never forwarded to the "duplicate.orders" queue.