Affects Version/s: 3.0.1
Fix Version/s: Tech. Debt
Component/s: Core: Routing / Filters
MULE-4333 idempotent-receiver-router does not allow custom object store in XML configuration MULE-3410 idempotent-receiver-router should have "disablePersistance" and "storePath" attributes in schema MULE-5798 Incorrect mail parsing with nested multipart MULE-3610 One Inbound endpoint Supports both synchronous and asynchronous routes MULE-6613 HTTP outbound stream mode doesn't work MULE-9321 CDATA in Weave map doesn't work MULE-661 Spring MuleEventMulticaster doesn't work MULE-5760 WeakHashMap in org.mule.module.scripting.expression.AbstractScriptExpressionEvaluator doesn't work MULE-3587 Custom ID stores on the IdempotentReceiver causes NullPointerException MULE-5476 processor expression evaluator doesn't work
Messages being stopped hby the idempotent-receiver-router aren't processed by the forwarding-catch-all-strategy. For instance, in the following config:
<add-message-property key="orderId" value="#[header:INBOUND:orderId]"/>
<vm:outbound-endpoint path="duplicate.orders" exchange-pattern="one-way"/>
A duplicate message is caught by the idempotent-receiver-router but never forwarded to the "duplicate.orders" queue.