You uses old versions of XML libraries like xerces 2.6.x and have mixed version of jdom, spring JARs and whatnot. All that can lead to a bit "unstable" deployment.
You may want to look at upgrading xerces and/or xalan etc. On Thu, Apr 25, 2013 at 10:24 PM, Christian Müller <christian.muel...@gmail.com> wrote: > Can you share the load test with us? Than we could may fix it if it's an > issue in Camel. > > Best, > Christian > > > On Thu, Apr 25, 2013 at 2:07 PM, gmdavidson62 <gmdavidso...@gmail.com>wrote: > >> FYI....we fixed this, changing the split strategy from an XPATH to a >> tokenized split. When we "load tested" our routes with both strategies, we >> were able to recreate the errors consistently with the XPATH split. When >> we >> changed to the tokenized split we never got an error, all >> splits/aggregations were successful. >> >> We didn't dig into the camel source....so just a guess, but seems to be a >> threading issue. We may have been able to fix this in other >> ways....upgrading JDK, Camel or adding a thread pool??? >> >> Error: >> No body available of type: java.lang.String but has value: [Policy: null] >> of >> type: org.apache.xerces.dom.DeferredElementNSImpl on: Message: >> ................ >> >> This is what we did, changed the split to use: >> <tokenize token="Policy" xml="true"/> >> instead of: >> <camel:xpath>/BOB-GetPoliciesByClientResponse/Policies/Policy</camel:xpath> >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/random-splitter-error-tp5731160p5731537.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
