My Oracle Support Banner

Oracle Purchasing OTM Integration - GLogService Failed With Error "Content is not allowed in prolog" (Doc ID 422425.1)

Last updated on SEPTEMBER 05, 2018

Applies to:

Oracle(R) BPEL Process Manager
Information in this document applies to any platform.
***Checked for relevance on 18-Jan-2012***

Symptoms

On 11.5.10.2 in Production:
When attempting to perform Oracle Purchasing - OTM integration using BPEL process "PoSendPoToOtm" the following error occurs.

ERROR
org.collaxa.thirdparty.dom4j.DocumentException: Error on line 1 of document : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.
at
com.collaxa.cube.ws.wsif.providers.http.WSIFOperation_HTTP.executeRequestResponseOperation(WSIFOperation_HTTP.java:385)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:453)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Symptoms
  Cause
  Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.