My Oracle Support Banner

Failure te Read WSDL When Using UDDI Over Non-blocking Invoke (Doc ID 850101.1)

Last updated on APRIL 01, 2019

Applies to:

Oracle(R) BPEL Process Manager 10g - Version to [Release AS10gR3]
Information in this document applies to any platform.
This problem can occur on any platform.


When using a UDDI registry to access a BPEL process via non-blocking invoke, the following exception is thrown. If standard, blocking invoke is used, the exception is not thrown and the WSDL is retrieved correctly from the service registry.

Your test request was processed synchronously. It took 369.0milliseconds to finish and generated the following output:
Value: <Fault xmlns=""
env="" >
<faultcode xmlns="" >:remoteFault</faultcode>
<faultstring xmlns="" >business exception</faultstring>
<faultactor xmlns="" >cx-fault-actor</faultactor>
<detail xmlns="" >
<summary>Failed to read wsdl. Error happened when reading wsdl at
_Main_v2009_04_20__62232_549d225c89c49afacf9c9d25d5351ac8.tmp/null", because "Failed to read wsdl file at:
nvoke_Main_v2009_04_20__62232_549d225c89c49afacf9c9d25d5351ac8.tmp/null", caused by: :
Main_v2009_04_20__62232_549d225c89c49afacf9c9d25d5351ac8.tmp/null (No such file or directory)".
Make sure wsdl exists at that URL and is valid. </summary>


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

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