camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gmdavidson62 <gmdavidso...@gmail.com>
Subject Re: random splitter error
Date Thu, 25 Apr 2013 12:07:45 GMT
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.

Mime
View raw message