Did you enable the option to let camel-jms serialize the exchange? You need to care about the the property value which could not be serialized if that option is turned on.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tuesday, July 16, 2013 at 10:07 PM, cristisor wrote: > It seems that I was trying to serialize the exchange properties, which is > nonsense because the exchange that arrives on the new route will contain > it's own properties, and everything was failing probably when trying to > serialize the following property: > *CamelFileExchangeFile=GenericFile[path\filename.txt]* > > I don't understand why this was happening but I will only send the > information that I need instead of sending everything. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Exceptions-when-aggregating-messages-tp5735523p5735728.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
