camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Resolved: (CAMEL-364) camel-mina if exchange failed then out could potentially be a copy of in
Date Sun, 09 Mar 2008 07:39:35 GMT


Claus Ibsen resolved CAMEL-364.

    Fix Version/s: 1.3.0
       Resolution: Fixed

Fixed with patch from CAMEL-375

> camel-mina if exchange failed then out could potentially be a copy of in
> ------------------------------------------------------------------------
>                 Key: CAMEL-364
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-mina
>    Affects Versions: 1.3.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.3.0
> Using the camel-mina component in synchronous mode (InOut exchange pattern) there is
a potential bug if eg a processor throws an exception.
> This is a failed delivery in camel. And out-of-the-box the default policy is to retry
up till 6 times. And if still failing camel-mina will continue and return a response to the
> The respons is a duplicate of the in body.
> A workaround is to set the out body to null immediately in your processor. If the body
is null before the exception is thrown then camel-mina will no return a response.
> To reproduce the bug see the MinaTcpWithInOutUsingPlainSocketTest and remove the setbody
null code below and the test should fail.
> {code}
>  else if ("force-exception".equals(in)) {
>                             // clear out before throwing exception
>                             e.getOut().setBody(null);
>                             throw new IllegalArgumentException("Forced exception");
>                         }
> {code}
> In MinaConsumer there is a TODO comment where the bug should be handled (from CAMEL-356)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message