Hi Its an Apache ActiveMQ setting (not Camel specific) that do not allow java serialized objects by default, and you need to configure it with the approved classes/packages.
If you want to help improve the docs at Apache Camel, then you can submit a PR with doc updates on this file https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc And how to contribute to Camel is here http://camel.apache.org/contributing On Mon, Jan 15, 2018 at 10:34 AM, Leber, Thomas <thomas.le...@omnetric.com> wrote: > Hi, > > I'm sending in an onException clause the exchange to another camel route via > JMS. > In order to handle the error, the idea was to use transferExchange=true, > since the documentations states the exchange exception is transferred as well. > > Unfortunately I get this error in the JMS listener: > -------------------------------------------------------------------------------------------------------- > Execution of JMS message listener failed. Caused by: > [org.apache.camel.RuntimeCamelException - Failed to extract body due to: > javax.jms.JMSException: Failed to build body from content. Serializable class > not available to broker. Reason: java.lang.ClassNotFoundException: Forbidden > class org.apache.camel.impl.DefaultExchangeHolder! This class is not trusted > to be serialized as ObjectMessage payload. Please take a look at > http://activemq.apache.org/objectmessage.html for more information on how to > configure trusted classes.. > -------------------------------------------------------------------------------------------------------- > > I found out that there is a way to configure the security settings on the > AMQ, but I was surprised that this is not mentioned somewhere. > Did anybody else encounter this problem? > > Camel 2.17.0 > AMQ 5.11.0 > > Regards, > Thomas Leber -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
