camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: Message loss with transacted CXF consumer
Date Wed, 02 May 2012 17:33:21 GMT

Can you try setting the property:

org.apache.cxf.interceptor.USE_ORIGINAL_THREAD, "true"

on the CXF endpoint and seeing if that helps?   That should keep the request 
on the original thread and should allow the stack for that to unwind on an 
exception.

Dan


On Wednesday, May 02, 2012 04:36:35 PM Stefan Burkard wrote:
> Hi
> 
> The facts:
> - InOnly route
> - CXF bean consumes with "transacted" from JMS queue
> => therefore I expect the message to succeed or to go to JMS-DLQ
> 
> Result: CXF consumer commits JMS message in any case - no matter if
> exceptions occur in route. If an error occurs during route processing
> the message is lost.
> 
> Conclusion: "transacted" is currently useless if CXF is used with InOnly
> Suggestions: Mark the route as InOut => did not help
> 
> Attached is a small maven project that illustrates the problem with
> unittests.
> 
> One solution would of course be to handle ALL route errors with a
> Camel error handler, but this is more of a workaround. I am wondering
> if there is a real solution for this problem.
> 
> Thanks
> Stefan
-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


Mime
View raw message