Follow Us on Twitter

OSB, For-Each and the org.apache.xmlbeans.impl.values.XmlValueDisconnectedException exception

by Laurens van der Starre on May 16, 2013 · 0 comments

At one of my clients a developer was hitting the following BEA-382000 error in a OSB proxy:

                at org.apache.xmlbeans.impl.values.XmlObjectBase.check_orphaned(
                at org.apache.xmlbeans.impl.values.XmlObjectBase.newCursor(
                at stages.transform.runtime.ForEachMessageContext.initVariableValue(
                at stages.transform.runtime.ForEachRuntimeStep.processMessage(

The exception occurred from within a For-Each operation within the proxy pipeline, in which a Service Callout was invoked multiple times and its output concatenated into the $body.

Fearing for a bug in Apache’s XMLBeans, I was relieved to find out that the cause was much more innocent: when using a For-Each operation in which a ServiceCallout is done, don’t manipulate the $body context variable. Use a (temporary) copy, and assign the results afterwards outside of the For-Each. Then you should be fine.

Happy coding!

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

{ 0 comments… add one now }

Leave a Comment


Previous post:

Next post:

About Whitehorses
Company profile

Whitehorses website

Home page

Follow us
Blog post RSS
Comment RSS