Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

XML-22900: (Fatal Error) An internal error condition occurred in transformation

user11179792Sep 9 2013 — edited Feb 26 2020

Hi Gurus,

In my BPEL process, I have an XSLT transformation to copy existing task comments to the input of a new task (initialTaskInput.payload). The same XSLT transformation is used in a similar BPEL process with the same input and output payload and it works fine there.The process is deployed successfully. However,I ran into the following error at run-time. I searched OTN before creating the new post. I tried a few possible solutions including re-generating the xsl file, deploying using a new revision number and setting to use the XSLT 2.0 style-sheet. It seems the problem still lingers. It would be great if any of you could point me to the right direction.

The following exception occurred while attempting to execute operation copy at line 575

-<exception class="com.collaxa.cube.xml.xpath.XPathException">

-<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">

<h3>

This page contains the following errors:

</h3>

error on line 7 at column 1: Extra content at the end of the document

</div>

<h3>

Below is a rendering of the page up to the first error.

</h3>

</parsererror>

XPath expression failed to execute. An error occurs while processing the XPath expression; the expression is ora:doXSLTransformForDoc('xsl/Transformation_CopyCommentsToNewTask2.xsl', $initiateTaskInput.payload, 'UserComments', $UserComments). The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: XML-22900: (Fatal Error) An internal error condition occurred.. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.

-<stack>

<f>

com.collaxa.cube.xml.xpath.BPELXPathUtil.evaluate#268

</f><f>

com.collaxa.cube.engine.ext.bpel.common.BPELWMPHelper.evalFromValue#383

</f><f>

com.collaxa.cube.engine.ext.bpel.v1.wmp.BPEL1AssignWMP.__executeStatements#138

</f><f>

com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#173

</f><f>

com.collaxa.cube.engine.CubeEngine.performActivity#2718

</f><f>

com.collaxa.cube.engine.CubeEngine._handleWorkItem#1197

</f><f>

com.collaxa.cube.engine.CubeEngine.handleWorkItem#1100

</f><f>

com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#78

</f><f>

com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#251

</f><f>

com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#330

</f><f>

com.collaxa.cube.engine.CubeEngine.endRequest#4652

</f><f>

com.collaxa.cube.engine.CubeEngine.endRequest#4584

</f><f>

com.collaxa.cube.engine.CubeEngine._callbackPerformer#1411

</f><f>

com.collaxa.cube.engine.CubeEngine.callbackPerformer#1340

</f><f>

com.collaxa.cube.engine.delivery.DeliveryHelper.callbackPerformer#396

</f><f>

com.collaxa.cube.engine.delivery.DeliveryService.handleCallback#812

</f><f>

...

</f>

</stack>

</exception>

Locked Post

New comments cannot be posted to this locked post.

Locked on Oct 8 2013

Added on Sep 9 2013

#business-process-management-suite, #soa-process-management

1 comment

3,247 views