Normally CamelExecutionExceptions wrap the actual exception inside it as a cause. Is your log not outputting the cause exception? If not, you can try to insert a Processor to explore the exception.getCause().
*Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Wed, Sep 9, 2015 at 4:59 PM, Sashimi <[email protected]> wrote: > Hi during the trasmission of a message i get this error: > > < > http://camel.465427.n5.nabble.com/file/n5771388/Schermata_2015-09-09_alle_17.png > > > > the strange thing is that if I send (in the body message) a very similar > object (but smaller) this work > perfectly. > > I'm wondering if the problem is the objects size (the second one is > smaller) > or something that in the first object is not serializable. > Before i send my configurations i would like to know if there are size > limitations for sending objects? > > thank you very much. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/CamelExecutionException-Exception-occurred-during-execution-on-the-exchange-tp5771388.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
