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:

org.apache.xmlbeans.impl.values.XmlValueDisconnectedException
                at org.apache.xmlbeans.impl.values.XmlObjectBase.check_orphaned(XmlObjectBase.java:1258)
                at org.apache.xmlbeans.impl.values.XmlObjectBase.newCursor(XmlObjectBase.java:286)
                at stages.transform.runtime.ForEachMessageContext.initVariableValue(ForEachMessageContext.java:80)
                at stages.transform.runtime.ForEachRuntimeStep.processMessage(ForEachRuntimeStep.java:95)
                at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)

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!


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

Leave a Reply

Your email address will not be published. Required fields are marked *

*

* Copy This Password *

* Type Or Paste Password Here *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

 

Previous post:

Next post:

About Whitehorses
Company profile
Services
Technology

Whitehorses website

Home page
Whitebooks
Jobs

Follow us
Blog post RSS
Comment RSS
Twitter