workaround for CAMEL-4264

[David Tombs <cy...@gmail.com>]

Hi Camel folks,

I'm currently struggling from CAMEL4264[1] in  route that looks like:

JMS -> log -> stream resequencer -> log -> processor

Unfortunately, the exception is thrown between the 2nd log and
processor, and caught and logged (at DEBUG level!) by the
StreamResequencer. So the affected message is effectively dropped...
not even sent to the error handler for the route.

Can anybody think of a workaround for this before a new version is
released with the fix?

Thanks in advance,
David

[1] https://issues.apache.org/jira/browse/CAMEL-4264

-- 
Wise men _still_ seek Him.

Re: workaround for CAMEL-4264

[Willem Jiang <wi...@gmail.com>]

Hi David,

Sorry, I don't think there is a way to workaround this issue.
I just merged the patch into Camel 2.8.x, and we are planing the release 
Camel 2.8.1 recently.

On 8/26/11 2:30 AM, David Tombs wrote:
> Hi Camel folks,
>
> I'm currently struggling from CAMEL4264[1] in  route that looks like:
>
> JMS ->  log ->  stream resequencer ->  log ->  processor
>
> Unfortunately, the exception is thrown between the 2nd log and
> processor, and caught and logged (at DEBUG level!) by the
> StreamResequencer. So the affected message is effectively dropped...
> not even sent to the error handler for the route.
>
> Can anybody think of a workaround for this before a new version is
> released with the fix?
>
> Thanks in advance,
> David
>
> [1] https://issues.apache.org/jira/browse/CAMEL-4264
>


-- 
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
          http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang