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

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.1 to 10.1.3.5.0 - Release: AS10gR3 to
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:

<2010-06-01 09:27:41,227> <INFO> <collaxa> <ServerManager::__init>
*****************************************************************************
Oracle BPEL Server version 10.1.3.4.0
Build: 0
Build time: Fri May 01 18:07:27 PDT 2009
Build type: release
Source tag: PCBPEL_10.1.3.4.0MLR9_GENERIC_RELEASE

<2010-06-01 09:27:41,469> <INFO> <collaxa> <ServerDescriptorManager::create> Detected server descriptor version '2.0.2'
<2010-06-01 09:27:41,516> <INFO> <collaxa> <ServerAdaptorManager::logJVMInformation>
*****************************************************************************

<2010-06-01 09:31:37,044> <ERROR> <default.collaxa.cube.activation>[PullPushAdapterThread] <AdapterFramework::Inbound> Error while performing endpoint Activation: ORABPEL-12537
XSD Loading problem.
Unable to load Translation schemas from for http://xmlns.oracle.com/A7/POInput due to: XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.

Please make sure all used XML schemas are imported/included correctly.
[Caused by: XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.
]
<2010-06-01 09:31:37,045> <ERROR> <default.collaxa.cube.activation>[PullPushAdapterThread] <AdapterFramework::Inbound> JCAActivationAgent:viewAccepted - AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter File Adapter was unable to activate the endpoint oracle.tip.adapter.file.inbound.FileActivationSpec:{OpaqueSchema=false, MinimumAge=200, IncludeFiles=POInput_.*\.xml, PhysicalDirectory=/home/oracle/inbound, DeleteFile=true, PollingFrequency=120, PhysicalArchiveDirectory=/home/oracle/archive} due to the following reason: ORABPEL-12537
XSD Loading problem.
Unable to load Translation schemas from for http://xmlns.oracle.com/A7/POInput due to: XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.

Please make sure all used XML schemas are imported/included correctly.
[Caused by: XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.
]
Please correct the reported issue and redeploy the BPEL process.

<2010-06-01 09:31:37,045> <ERROR> <default.collaxa.cube.activation>[PullPushAdapterThread] <AdapterFramework::Inbound>
ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter File Adapter was unable to activate the endpoint oracle.tip.adapter.file.inbound.FileActivationSpec:{OpaqueSchema=false, MinimumAge=200, IncludeFiles=POReceived_.*\.xml, PhysicalDirectory=/home/oracle/inbound, DeleteFile=true, PollingFrequency=120, PhysicalArchiveDirectory=/home/oracle/archive} due to the following reason: ORABPEL-12537
XSD Loading problem.
Unable to load Translation schemas from for http://xmlns.oracle.com/A7/POInput due to: XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.

Please make sure all used XML schemas are imported/included correctly.
[Caused by: XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.
]
Please correct the reported issue and redeploy the BPEL process.

at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:569)
at oracle.tip.adapter.fw.agent.jca.JCAActivationAgent.performEndpointActivation(JCAActivationAgent.java:1076)
at oracle.tip.adapter.fw.agent.jca.JCAActivationAgent.activateInboundJcaEndpoint(JCAActivationAgent.java:1059)
at oracle.tip.adapter.fw.agent.jca.JCAActivationAgent.viewAccepted(JCAActivationAgent.java:1560)
at org.collaxa.thirdparty.jgroups.blocks.PullPushAdapter.notifyViewChange(PullPushAdapter.java:302)
at org.collaxa.thirdparty.jgroups.blocks.PullPushAdapter.run(PullPushAdapter.java:238)
at java.lang.Thread.run(Thread.java:595)
Caused by: ORABPEL-12537
XSD Loading problem.
Unable to load Translation schemas from for http://xmlns.oracle.com/A7/POInput due to: XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.

Please make sure all used XML schemas are imported/included correctly.

at oracle.tip.adapter.fw.wsdl.WSDLUtils.getTypesSchemas(WSDLUtils.java:1504)
at oracle.tip.adapter.fw.wsdl.WSDLUtils.setupSpecForTranslation(WSDLUtils.java:1393)
at oracle.tip.adapter.fw.jca.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:439)
... 6 more
Caused by: ORABPEL-12534
XSD Location problem.
No XSD (XML Schema) found for target namespace http://xmlns.oracle.com/A7/POInput and input element INPUT_INTERFACE
Please make sure the WSDL message points to a valid type.

at oracle.tip.adapter.fw.wsdl.WSDLUtils.getTypesSchemas(WSDLUtils.java:1489)
... 8 more


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://test.us.oracle.com: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

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms