On Wed, Jun 8, 2011 at 5:31 PM, gsilverman
wrote:
> I have the following route which uses stopOnException to catch exceptions:
>
>
>
> parallelProcessing="true" stopOnException="true">
>
>
>
>
>
>
> The processSegment bean in the
I don't believe the AggregatorStrategy is the problem, but here is mine:
public class DispensingAggregationStrategy implements AggregationStrategy{
public Exchange aggregate(Exchange oldExchange, Exchange newExchange)
{
if (oldExchange == null)
I cannot reproduce this on trunk. What do you do in that custom
aggregatorStrategy you do?
On Wed, Jun 8, 2011 at 5:31 PM, gsilverman
wrote:
> I have the following route which uses stopOnException to catch exceptions:
>
>
>
> parallelProcessing="true" stopOnException="true">
>
I have created a ticket to improve this
https://issues.apache.org/jira/browse/CAMEL-4080
On Thu, Jun 9, 2011 at 5:36 PM, Claus Ibsen wrote:
> When moving to the DLQ there is no caused exception attached and
> whatnot. Its the original message *as is*.
>
>
> On Thu, Jun 9, 2011 at 5:15 PM, gsilve
So, if I understand you correctly, I shouldn't use the DeadLetterChannel type
in the error handler. What types are available and how would I then
configure the error handler?
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitter-StopOnException-doesn-t-forward-the-exception-
When moving to the DLQ there is no caused exception attached and
whatnot. Its the original message *as is*.
On Thu, Jun 9, 2011 at 5:15 PM, gsilverman
wrote:
> Yes. I'm using camel v2.71.
>
> Here is my error handler:
>
> deadLetterUri="direct:queryFormularyError" useOriginalMessage="tru
Yes. I'm using camel v2.71.
Here is my error handler:
and the deadletter route is:
The queryFormularyErrorHandler refers to the QueryFormularyErrorHandler
processor described earlier, and the createReturnMsg bean just translates
the exception message into a
Hi
Can you post more details about how you configured the error handler?
And what version of Camel are you using?
On Wed, Jun 8, 2011 at 5:31 PM, gsilverman
wrote:
> I have the following route which uses stopOnException to catch exceptions:
>
>
>
> parallelProcessing="true" stopO
