I was also very surprised myself. This is a good idea to have modular architecture where the application is deployed as separate bundles but when you have to redeploy or update part of a project, sometimes you forget to check / verify this kind of configuration defined in a xml file embedded in a jar of the infra.
Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com twitter : http://twitter.com/cmoulliard On Thu, Oct 8, 2009 at 9:46 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Thu, Oct 8, 2009 at 9:44 AM, Charles Moulliard <cmoulli...@gmail.com> > wrote: >> Forget my post. The maximum redeliveries was not setted to ZERO but 1. >> > > Great that you found the issue. And glad it seems to work. As we do > got a ton of testing in this area so I was a bit surprised if there > was an issue. > >> Charles Moulliard >> Senior Enterprise Architect >> Apache Camel Committer >> >> ***************************** >> blog : http://cmoulliard.blogspot.com >> twitter : http://twitter.com/cmoulliard >> >> >> >> On Tue, Oct 6, 2009 at 5:46 PM, Charles Moulliard <cmoulli...@gmail.com> >> wrote: >>> I'm faced to a strange problem. I see that a message posted in a queue >>> is processed twice in a Camel route after an error has been raised >>> with a rollback >>> >>> queueRequestEndpoint = activemq:x3s:request >>> queueReportingEndpoint = activemq:x3s:reporting >>> queueRequestMessageEndpoint = activemq:x3s:requestmessage >>> >>> Here is the route : >>> >>> <camel:route errorHandlerRef="txErrorHandler"> >>> <camel:from ref="queueRequestEndpoint" /> >>> <camel:transacted ref="PROPAGATION_REQUIRED"/> >>> <camel:doTry> >>> >>> <camel:convertBodyTo >>> type="com.xpectis.x3s.platform.model.Request" /> >>> >>> <camel:bean ref="serviceHelper" >>> method="generateException"/> >>> >>> <camel:bean ref="serviceHelper" >>> method="parseRequest" /> >>> >>> <camel:to ref="queueRequestMessageEndpoint" >>> /> >>> >>> <camel:doCatch> >>> >>> <camel:exception>com.xpectis.x3s.exception.X3SClientException</camel:exception> >>> <camel:bean ref="serviceHelper" >>> method="processException" /> >>> <camel:to >>> ref="queueReportingEndpoint" /> >>> </camel:doCatch> >>> >>> <camel:doCatch> >>> >>> <camel:exception>com.xpectis.x3s.exception.X3STechnicalException</camel:exception> >>> <camel:to >>> uri="log:com.xpectis.x3s?level=INFO&multiline=true&showException=true&showCaughtException=true&showStackTrace=true" >>> /> --> >>> <camel:rollback/> >>> </camel:doCatch> >>> </camel:doTry> >>> >>> </camel:route> >>> >>> >>> Charles Moulliard >>> Senior Enterprise Architect >>> Apache Camel Committer >>> >>> ***************************** >>> blog : http://cmoulliard.blogspot.com >>> twitter : http://twitter.com/cmoulliard >>> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus >
