[
https://issues.apache.org/activemq/browse/CAMEL-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-2616:
-------------------------------
Comment: was deleted
(was: Wiki documentation pending
h3. Delayed redelivery
>From *Camel 2.4* onwards Camel will *not block* while waiting for a delayed
>redelivery to occur (its asynchronous). However if you use transacted routes
>then Camel will block as its mandated by the transaction manager to execute
>all the work in the same thread context. You can disable the non blocking
>behavior by the {{syncDelayedRedelivery}} option, which instructs Camel to
>always block while waiting. This occurs synchronously in the same thread.
Since Camel by default is asynchronous for delayed redelivery it could occur
that a message is to be redelivered, and while it waits, the route could pickup
a new message and have it routed successfully. This can cause out of order of
messaging, as the redelivered message will then be completed _after_ that 2nd
message. To avoid this you have to enable the {{syncDelayedRedelivery}} option.)
> RedeliveryErrorHandler - Add option to let delayed Exchange be non blocked
> --------------------------------------------------------------------------
>
> Key: CAMEL-2616
> URL: https://issues.apache.org/activemq/browse/CAMEL-2616
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
>
> See nabble
> http://old.nabble.com/Message-blocks-route-until-all-redelivery-attempts-are-exhausted-ts28123035.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
