My Oracle Support Banner

Container Startup Returns ORABPEL-12537 XSD Loading problem, ORABPEL-12517 and ORABPEL-12534 (Doc ID 1201624.1)

Last updated on APRIL 16, 2021

Applies to:

Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 to 10.1.3.5.0
Information in this document applies to any platform.

Symptoms

When starting the BPEL server in a 10g system a Polling Adapter Endpoint fails to start since it cannot find a XSD reference that exists in its WSDL file. The WSDL file and XSD file are both local to the BPEL server. This is only seen during container startup. To activate the Polling Adapter Endpoint the following workaround is used after system startup completes:

From the BPELConsole:
1. Make the process Retired and Off.
2. Clear the WSDL Cache.
3. Make the process Active and On.

During startup a similar error is seen in the logfile $ORACLE_HOME/opmn/logs/*_*~*_*~*_group~*.log:



The logfile shows a problem with the element INPUT_INTERFACE. Checking this part of the adapter WSDL file A5POInputs.xsd defines the INPUT_INTERFACE:

...
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/file/" location="fileAdapterInboundHeader.wsdl"/>
<import namespace="http://schemas.oracle.com/bpel/extension" location="http://hostname:7777/orabpel/xmllib/RuntimeFault.wsdl"/>
<types>
     <schema xmlns="http://www.w3.org/2001/XMLSchema" >
         <import namespace="http://xmlns.oracle.com/A5/POInputs" schemaLocation="A5POInputs.xsd" />
         <import namespace="http://schemas.oracle.com/service/bpel/common" schemaLocation="XSLParams.xsd" />
     </schema>
</types>
...

From A5POInputs.xsd, INPUT_INTERFACE is defined:

...
<xs:element name="INPUT_INTERFACE">
     <xs:complexType>
         <xs:sequence>
             <xs:choice maxOccurs="unbounded">
                 <xs:element ref="RECHDR" maxOccurs="unbounded"/>
                 <xs:element ref="RECDTL" maxOccurs="unbounded"/>
                 <xs:element ref="HEADER" maxOccurs="unbounded"/>
             </xs:choice>
         </xs:sequence>
     </xs:complexType>
</xs:element>
...

As can been seen by this construction everything related to INPUT_INTERFACE is defined locally to the local process so it does not make sense that INPUT_INTERFACE cannot be found at startup time.

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


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