A fix would surely be in camel-core. But i don't know what fix it is. You can diff 2.8.x with working 2.9.x in camel-core, and maybe home into what commit fixed it.
If you are a Red Hat customer you can get support on your issue with the Fuse ESB product. If not you are on your own :) On Thu, Nov 28, 2013 at 10:46 AM, Stephan Burkard <sburk...@gmail.com> wrote: > Hi Claus > > I also tried with Camel 2.9.x and this works as expected. Problem is that > we use a combined FUSE distribution (Servicemix, Camel, CXF, ...) and from > there we get Camel version "camel-2.8.0-fuse-02-05". I don't know if Camel > 2.9 is compatible with the other framwork-versions of fuse-02-05. > > Can you give me a hint, which JAR was modified to implement this Bugfix? > camel-core? camel-jms? both? Then I could perhaps embed this JAR into the > affected OSGi bundle as a "patch" without changing the whole platform we > are running on. > > Thanks a lot > Stephan > > > On Thu, Nov 28, 2013 at 8:57 AM, Stephan Burkard <sburk...@gmail.com> wrote: > >> Hi Claus >> >> I tried with 2.8.6 but I get the same error. >> >> Regards >> Stephan >> >> >> >> On Thu, Nov 28, 2013 at 7:58 AM, Claus Ibsen <claus.ib...@gmail.com>wrote: >> >>> Try with latest 2.8.x release >>> >>> On Wed, Nov 27, 2013 at 5:25 PM, Stephan Burkard <sburk...@gmail.com> >>> wrote: >>> > Hi Camel users >>> > >>> > I have a strange behavior with Camel 2.8.0. I have attached a small >>> > example-project that has three flavors of the same Camel route. >>> > >>> > - One without errorhandling >>> > - One with two errorhandlers >>> > - One with two errorhandlers and an onException handler >>> > >>> > All of them have a corresponding test class to run them. >>> > >>> > The first two are running fine, in the third I use an additional >>> onException >>> > handler to catch and handle a specific exception. >>> > >>> > As a final step of this handler, I forward the messages to another >>> endpoint. >>> > I tried to(mock:...), to(activemq:queue:...), to(bean:...), >>> wireTap(...) but >>> > all of them are causing the error message "SendProcessor has not been >>> > started". >>> > >>> > I found a similar case ( >>> https://issues.apache.org/jira/browse/CAMEL-4107), >>> > but this should be fixed in version 2.8.0. >>> > >>> > Is this another flavor of this Issue or am I doing something totally >>> wrong? >>> > >>> > Thanks for any help >>> > Stephan >>> > >>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> Red Hat, Inc. >>> Email: cib...@redhat.com >>> Twitter: davsclaus >>> Blog: http://davsclaus.com >>> Author of Camel in Action: http://www.manning.com/ibsen >>> >> >> -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
