Error Orabpel 10903 failed to read wsdl - please help me

Dear Experts,
I am struggling hard with these errors. Actually I am having 7 bpel process, one among that 7 integrates all the process. I have deployed and tested in my machine it is working perfectly fine. I just copy the entire set up to another machine with same server version as SOA 10.1.3.1 and JDeveloper 10.1.3.1. But I am receiving error. Also I have made all the required changes respective to new server. In the sense have change wsdl location respective to new server. But I am able to compile/deploy all the process except the integrated process. Even I am not able to compile the integrated process. Please suggest me. what else i have to change..?
Error:
[Error ORABPEL-10903]: failed to read wsdl
[Description]: in "bpel.xml", Error loading schemas from wsdl.
Error while loading schemas from wsdl file at location "http://eway-pc:8889/orabpel/default/RecommendProcess/RecommendProcess?wsdl". The reason is http://eway-PC:8889/orabpel/xmllib/ws-addressing.xsd.
Please verify the schemas defined in wsdl.
[Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
Thanks,
Rajesh A

Hai Rajesh its not a bug. If you see the wsdl file used in your partner link. you can see this
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://localhost.com:8888/orabpel/xmllib/ws-addressing.xsd"/>
</schema>
so while you try to deploy in your system schema location will schemaLocation="http://localhost.com:8888/orabpel/xmllib/ws-addressing.xsd" will be available bu if you try to deploy in other system you cant deploy because it wont be available.
Fix
copy the file int your project and change the wsdl to
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="ws-addressing.xsd"/>
</schema>
Also refer the threads
could not deploy my project in unix environment
Re: Is there an equivalent of Properties File for BPEL??

Similar Messages

  • Error:   [Error ORABPEL-10903]: failed to read wsdl

    Can any one please explain this error, When ever I used to change the XSD file of the process I am getting this error. Dont know why?? Please suggest me
    Error:
    [Error ORABPEL-10903]: failed to read wsdl
    [Description]: in "bpel.xml", Global Type declaration/definition of name '{http://xmlns.oracle.com/bpel/workflow/task}actionType' are duplicated at the following locations:
    file:/F:/JDeveloper/jdev/mywork/TestApplications/UploadProcess/bpel/WorkflowTask.xsd [line#: 151]
    file:/F:/JDeveloper/jdev/mywork/TestApplications/UploadProcess/bpel/TaskService.xsd [line#: 307]
    There are at least two of them looking different:
    file:/F:/JDeveloper/jdev/mywork/TestApplications/UploadProcess/bpel/WorkflowTask.xsd [difference starting at line#:151]
    file:/F:/JDeveloper/jdev/mywork/TestApplications/UploadProcess/bpel/TaskService.xsd [difference starting at line#:307]
    [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
    Thanks,
    Rajesh

    Rajesh,
    Let's take an example. There are 2 BPEL process's, BPEL1 and BPEL2 in which bpel1 invokes the bpel2. Whenever a schema (ex: test.xsd) used in bpel1 is referred in bpel2, if you are making any change in the schema in bpel1 and try to deploy it, it gives the Error ORABPEL-10903....
    Solution is
    1. you need to copy the changed test.xsd in bpel1 to bpel2.
    2. Deploy the bpel2
    3. deploy bpel1
    Hope this would help.
    Thanks,
    Sen.

  • [Error ORABPEL-10903]: failed to read wsdl

    Hi,
    I am trying to deploy the Order booking application in Oracle SOA suite (10.1.3.2.0), and while deploying the SOAOrderBooking BPEL application to the application server, i get this error. I am following the SOA demo guide to deploy this sample application step-by-step.
    I can access the 2 URLS -
    a) http://localhost:8888/orabpel/default/SelectManufacturer/1.0/SelectManufacturer?wsdl
    b) http://KOLDXP-SHASEN:8888/orabpel/xmllib/ws-addressing.xsd
    in the browser.
    Can anyone suggest me the solution to this ?? What am I missing? The ports are all default ones and I did a basic installation.
    Thanks,
    Shantonav
    | Compiling bpel process SOAOrderBooking, revision 1.0
    [bpelc] ORABPEL-01021
    [bpelc]
    [bpelc] BPEL validation failed.
    [bpelc] BPEL source validation failed, the errors are:
    [bpelc]
    [bpelc] [Error ORABPEL-10903]: failed to read wsdl
    [bpelc] [Description]: in "bpel.xml", Error loading schemas from wsdl.
    [bpelc] Error while loading schemas from wsdl file at location "http://localhost:8888/orabpel/default/SelectManufacturer/1.0/SelectManufacturer?wsdl". The reason is http://KOLDXP-SHASEN:8888/orabpel/xmllib/ws-addressing.xsd.
    [bpelc] Please verify the schemas defined in wsdl.
    [bpelc] .
    [bpelc] [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
    [bpelc] .
    [bpelc]
    [bpelc]      at com.collaxa.cube.lang.compiler.CubeProcessor.validateClientSide(CubeProcessor.java:1133)
    [bpelc]      at com.collaxa.cube.lang.compiler.CubeProcessor.transformClientSide(CubeProcessor.java:449)
    [bpelc]      at com.collaxa.cube.lang.compiler.CubeParserHelper.compileClientSide(CubeParserHelper.java:83)
    [bpelc]      at com.collaxa.cube.ant.taskdefs.Bpelc.execute(Bpelc.java:626)
    [bpelc]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    [bpelc]      at org.apache.tools.ant.Task.perform(Task.java:364)
    [bpelc]      at org.apache.tools.ant.Target.execute(Target.java:341)
    [bpelc]      at org.apache.tools.ant.Target.performTasks(Target.java:369)
    [bpelc]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    [bpelc]      at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
    [bpelc]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
    [bpelc]      at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    [bpelc]      at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
    [bpelc]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [bpelc]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [bpelc]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [bpelc]      at java.lang.reflect.Method.invoke(Method.java:585)
    [bpelc]      at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
    [bpelc]      at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
    [bpelc]      at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
    [bpelc] BPEL validation failed.
    [bpelc] BPEL source validation failed, the errors are:
    [bpelc]
    [bpelc] [Error ORABPEL-10903]: failed to read wsdl
    [bpelc] [Description]: in "bpel.xml", Error loading schemas from wsdl.
    [bpelc] Error while loading schemas from wsdl file at location "http://localhost:8888/orabpel/default/SelectManufacturer/1.0/SelectManufacturer?wsdl". The reason is http://KOLDXP-SHASEN:8888/orabpel/xmllib/ws-addressing.xsd.
    [bpelc] Please verify the schemas defined in wsdl.
    [bpelc] .
    [bpelc] [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
    [bpelc] .
    [bpelc]
    BUILD FAILED
    D:\soademo_101310_prod\SOADEMO\SOAOrderBooking\build.xml:72: Validation error

    Make sure you have turned off your proxy setting in JDeveloper. Tools -> Preferences -> Web & Proxy settings
    Are you sure that is the right version of SOA Suite?
    cheers
    James

  • ORABPEL-10903 failed to read wsdl

    I have a process flow that was working nicely. I added one property in an XML document and now the process won't compile. I have removed the new line and I still receive this error. The error is:
    Error: [Error ORABPEL-10903]: failed to read wsdl [Description]: in "bpel.xml", Error loading schemas from wsdl. Error while loading schemas from wsdl file at location "file:/C:/OraBPELPM_1/integration/jdev/jdev/mywork/SalesForceDemo/SalesForceCreate/SalesForceCreate.wsdl". The reason is no protocol: XMLSchema.dtd. Please verify the schemas defined in wsdl. . [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
    I don't know where to look to fix this problem. Does JDev keep some compiled classes around somewhere that need to be cleaned up? This is the second process that this has occurred on. The last time I had to recreate the entire process to get it working again.
    Any help would be greatly apprecated.

    Hi
    I am getting this error when I am trying to invoke a synshronous "CreditRating" service.
    A problem occured while connecting to server "localhost" using port "9700": bpel_myOrderBooking_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
    Error while loading process.
    The process domain encountered the following errors while loading the process "myOrderBooking" (revision "1.0"): Failed to read wsdl.
    Failed to read wsdl at "http://127.0.0.1:9700/orabpel/default/CreditRatingService/CreditRatingService?wsdl", because "Failed to read WSDL from http://127.0.0.1:9700/orabpel/default/CreditRatingService/CreditRatingService?wsdl: HTTP connection error code is 502".
    Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly.
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    Also,my Integration server connection is showing
    Application Server: OK
    BPEL Process Manager Server: OK
    ESB Server: FAILED
    Please help me out...

  • ORABPEL-10103  - failed to read wsdl

    Hi,
    I develop a first webservice (Employee). Then, I develop a second web service with a Partner Link to the first service... When I build the process, I obtain that error:
    Error ORABPEL-10103]: failed to read wsdl
    [bpelc] [Description]: Failed to read wsdl.
    [bpelc] Error happened when reading wsdl at "file://D:/MyWork/BPEL_workspace/Employee/Employee.wsdl", because "WSDLException: faultCode=PARSER_ERROR: Error reading file: D".
    [bpelc] Make sure wsdl exists at that URL and is valid.
    The url of the wsdl file is correct.
    The configuration of obsetenv.bat is
    OB_JAVA_PROPERTIES="-Djavax.wsdl.factory.WSDLFactory=oracle.j2ee.ws.wsdl.factory.WSDLFactoryImpl"
    PROXY_SET="[HTTP_PROXY_SET]"
    I configure the BPEL Designer (no proxy = localhost)
    Regards,
    Cyryl

    Hi,
    Thanks for your help. I deploy the first service. Then, in the second service, I replace the absolute wsdl file path by the url of the first service.
    Everything is working fine.
    Have a great day,
    Cyryl

  • Compilation error:  Failed to read wsdl

    Dear Experts,
    I am getting issue during deployment of BPEL process. I have created a BPEL process with schema named TD_Init.xsd and I get deployed. Later I have changed my xsd content in the sense I have added some more elements on the same xsd and update my process. getting compilation error as
    Error: [Error ORABPEL-10903]: failed to read wsdl
    [Description]: in "bpel.xml", Global element declaration/definition of name '{http://www.example.org}ProcessRequestElement' are duplicated at the following locations:
    file:/F:/JDeveloper/jdev/mywork/TDRequest/TDIntegration/bpel/TD_Init.xsd [line#: 14]
    http://eway:8889/orabpel/default/RecommendProcess/TD_Init.xsd [line#: 14]
    http://eway:8889/orabpel/default/AdvanceIssue/TD_Init.xsd [line#: 14]
    There are at least two of them looking different:
    file:/F:/JDeveloper/jdev/mywork/TDRequest/TDIntegration/bpel/TD_Init.xsd [difference starting at line#:23]
    http://eway:8889/orabpel/default/RecommendProcess/TD_Init.xsd [difference starting at line#:23]
    [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).

    Hi Rajesh,
    Thanks. You are having this issue because you are referencing the same xsd at a time with more than one process. Ensure that you reference the schema with its logical reference and use it within you local project directly. Even, if that does not work, then make it global and so all processes can use it .
    Example :
    You need to copy all your schemas into <ORACLE_SOA_HOME>/bpel/system/xmllib folder and access them using the following URL:
    http://<HOST NAME>:<PORT>/orabpel/xmllib/<XSD_PATH>
    For Example:
    http://localhost:7777/orabpel/xmllib/myxsd.xsd
    Regards
    A

  • Error ORABPEL-10903

    Hi,
    I am using eclipse version 0.9.13 and working through the creditflow example. I am getting the following error message on Windows 2000 using java 1.4
    Buildfile: C:\Documents and Settings\dkunzman\workspace\CreditFlow\build.xml
    main:
    [bpelc] BPEL validation failed.
    [bpelc] BPEL source validation failed, the errors are:
    [bpelc]
    [bpelc] [Error ORABPEL-10903]: failed to read wsdl
    [bpelc] [Description]: in "bpel.xml", Failed to read wsdl.
    [bpelc] Error happened when reading wsdl at "C:\Documents%20and%20Settings\dkunzman\workspace\CreditFlow\CreditFlow.wsdl", because "WSDLException: faultCode=INVALID_WSDL: Invalid XML in document at: file:/C:/Documents%20and%20Settings/dkunzman/workspace/CreditFlow/CreditFlow.wsdl: can't declare any more prefixes in this context".
    [bpelc] Make sure wsdl exists at that URL and is valid.
    [bpelc] .
    [bpelc] [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
    [bpelc] .
    BUILD FAILED
    C:\Documents and Settings\dkunzman\workspace\CreditFlow\build.xml:28: Validation error
    Total time: 2 seconds
    The wsdl exists but I do not know how to validate using free tools. Any idea? Also, I have checked it for well formedness adn that is ok.
    Any ideas?
    Doug

    This is the wsdl
    <?xml version="1.0"?>
    <definitions name="CreditFlow"
    targetNamespace="http://tutorial.oracle.com"
    xmlns:tns="http://tutorial.oracle.com"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    >
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    TYPE DEFINITION - List of services participating in this BPEL process
    The default output of the BPEL designer uses strings as input and
    output to the BPEL Process. But you can define or import any XML
    Schema type and us them as part of the message types.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <types>
    <schema attributeFormDefault="unqualified"
    elementFormDefault="qualified"
    targetNamespace="http://tutorial.oracle.com"
    xmlns="http://www.w3.org/2001/XMLSchema"
    >
    <element name="CreditFlowRequest">
    <complexType>
    <sequence>
    <element name="ssn" type="string" />
    </sequence>
    </complexType>
    </element>
    <element name="CreditFlowResponse">
    <complexType>
    <sequence>
    <element name="creditRating" type="int"/>
    </sequence>
    </complexType>
    </element>
    </schema>
    </types>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    MESSAGE TYPE DEFINITION - Definition of the message types used as
    part of the port type defintions
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <message name="CreditFlowRequestMessage">
    <part name="payload" element="tns:CreditFlowRequest"/>
    </message>
    <message name="CreditFlowResponseMessage">
    <part name="payload" element="tns:CreditFlowResponse"/>
    </message>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PORT TYPE DEFINITION - A port type groups a set of operations into
    a logical service unit.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <!-- portType implemented by the CreditFlow BPEL process -->
    <portType name="CreditFlow">
    <operation name="initiate">
    <input message="tns:CreditFlowRequestMessage"/>
    </operation>
    </portType>
    <!-- portType implemented by the requester of CreditFlow BPEL process
    for asynchronous callback purposes
    -->
    <portType name="CreditFlowCallback">
    <operation name="onResult">
    <input message="tns:CreditFlowResponseMessage"/>
    </operation>
    </portType>
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PARTNER LINK TYPE DEFINITION
    the CreditFlow partnerLinkType binds the provider and
    requester portType into an asynchronous conversation.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
    <plnk:partnerLinkType name="CreditFlow">
    <plnk:role name="CreditFlowProvider">
    <plnk:portType name="tns:CreditFlow"/>
    </plnk:role>
    <plnk:role name="CreditFlowRequester">
    <plnk:portType name="tns:CreditFlowCallback"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

  • Restart causing Failed to read wsdl and BaseScheduledWorker null pointer

    Hoped that 10.1.3.3.1 patchset would fix this but doesn't seem to have done so. I'm doing a test whereby I restart the application server under simulated load conditions, two BPEL domain log files are created, possibly indicating it has had a problem coming back up, domain.log.1 contains this :
    <2007-12-06 10:39:37,758> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception
    java.lang.NullPointerException
         at com.collaxa.cube.engine.dispatch.InstanceQueue.acknowledge(InstanceQueue.java:285)
         at com.collaxa.cube.engine.dispatch.BaseDispatchSet.acknowledge(BaseDispatchSet.java:241)
         at com.collaxa.cube.engine.dispatch.Dispatcher.acknowledge(Dispatcher.java:650)
    <2007-12-06 10:39:40,764> <ERROR> <default.collaxa.cube.engine> <CubeEngine::checkExpirable> Failed to unschedule work item "140957-BpInv3-BpSeq1.3-4" from the expiration agent.
    ORABPEL-00025
    Cannot unschedule agent.
    An attempt to unschedule the "expiration" agent with the scheduler has failed. The exception reported is: org.quartz.SchedulerException: Scheduler with name 'BPELPMRamScheduler' already exists.
         at org.quartz.impl.SchedulerRepository.bind(SchedulerRepository.java:87)
         at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:967)
    Async processes caught up in this are getting errors trying to pass back a response back to their invoking process as follows (note these processes work fine when I'm not restarting the app server underneath them) :
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>when invoking locally the endpoint 'http://pukldr00000.whatever.co.uk:7833/orabpel/default/invoker_name/1.0/processname/rolename', ; nested exception is:
         ORABPEL-00000
    Exception not handled by the Collaxa Cube system.
    An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-08003
    Failed to read wsdl.
    Failed to read wsdl at "http://pukldr00000.whatever.co.uk:7833/orabpel/default/processname/processname?wsdl", because "Failed to read WSDL from http://pukldr00000.whatever.co.uk:7833/orabpel/default/processname/processname?wsdl: HTTP connection error code is 500"
    Any help gratefully appreciated.

    SR has been filed for some time and includes an example. My example is as follows, async process A calls async process B, async process B just does a 20 second sleep in java before doing callback to A. To demonstrate the issue I just set off process A and shut down the oc4j through Enterprise Manager, process B hits the failed to read wsdl when it tries to callback to A. It seems like some of the infrastructure has been taken down before all of the in-memory processes have hit a dehydration point, which is not good !
    SR # is 6615784.993 I am now escalating.

  • Failed to read WSDL - connectException and unknownHostException

    Hi Guys,
    I am starting out with a new installation of SOA Suite 10g on my local windows machine.
    I've tested out a simple BPEL process deployment and all works fine.
    My next step is to test an Invoke of an external webservice: http://www.w3schools.com/webservices/tempconvert.asmx?WSDL
    Initially I had to setup proxy of my Jdev installation to get JDev to look at this WSDL (could not validate the WSDL without this):
    Proxy: 10.176.227.40
    Port: 8080
    Exceptions: |D701341|d701341|localhost
    But when I tried to deploy the BPEL process from jDev, I got an UnknownHostException:
    BUILD FAILED
    C:\jdev10g\jdev\mywork\NetworkRailSHLApplication\Pilot2\build.xml:78: A problem occured while connecting to server "localhost" using port "8888": bpel_Pilot2_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
    Error while loading process.
    The process domain encountered the following errors while loading the process "Pilot2" (revision "1.0"): Failed to read wsdl.
    Error happened when reading wsdl at "C:\soa10gdemo\bpel\domains\default\tmp\.bpel_Pilot2_1.0_e0b22fe325615e2ac6bf1710ef089616.tmp\ExternalWS.wsdl", because "Error reading import of file:/C:/soa10gdemo/bpel/domains/default/tmp/.bpel_Pilot2_1.0_e0b22fe325615e2ac6bf1710ef089616.tmp/ExternalWS.wsdl: Failed to read wsdl file at: "http://www.w3schools.com/webservices/tempconvert.asmx?WSDL", caused by: java.net.UnknownHostException. : www.w3schools.com: www.w3schools.com".
    Make sure wsdl exists at that URL and is valid.
    After searching a bit on the forums, found out that I might have to fiddle with my HOSTS file: C:\WINNT\system32\drivers\etc\hosts
    I added the following line to my hosts file:
    127.0.0.1 localhost
    216.128.29.26     www.w3schools.com
    This time when I tried to deploy the same process, got a ConnectException:
    BUILD FAILED
    C:\jdev10g\jdev\mywork\NetworkRailSHLApplication\Pilot2\build.xml:78: A problem occured while connecting to server "localhost" using port "8888": bpel_Pilot2_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
    Error while loading process.
    The process domain encountered the following errors while loading the process "Pilot2" (revision "1.0"): Failed to read wsdl.
    Error happened when reading wsdl at "C:\soa10gdemo\bpel\domains\default\tmp\.bpel_Pilot2_1.0_e0b22fe325615e2ac6bf1710ef089616.tmp\ExternalWS.wsdl", because "Error reading import of file:/C:/soa10gdemo/bpel/domains/default/tmp/.bpel_Pilot2_1.0_e0b22fe325615e2ac6bf1710ef089616.tmp/ExternalWS.wsdl: Failed to read wsdl file at: "http://www.w3schools.com/webservices/tempconvert.asmx?WSDL", caused by: java.net.ConnectException. : Connection timed out: connect".
    Make sure wsdl exists at that URL and is valid.
    I can visit view WSDL from my Internet Explorer with the same proxy config as mentioned above.
    I am not sure how do I get my local SOA Suite to talk to the external web service.
    Could someone point me in the right direction please?
    Thanks,
    Ravi

    I am also facing the similar kind of issue. Please suggest a solution

  • BPEL Cluster: Failed to read wsdl

    I want to start a bpel process over the dashboard from bpel pm.
    If i click the bpel process on the dashboad, i get a timeout with the following error message:
    Failed to read wsdl file at: "http://10.0.0.211:7778/orabpel/default/BPELCluster/1.0/BPELCluster?wsdl", caused by: java.net.SocketException. : Connection reset
    But if i put the link into the same browser, i get the WSDL immediately.
    10.0.0.211 is the ip of my load balancer....
    Any comments?

    I'm also facing the same exact error after clustering the BPEL Process Manager.
    Were you able to solve this issue.
    Please share your thoughts.

  • Urgent: Failed to read WSDL

    Hi,
    I am getting error in our production system similar to below error whenever the load in the server is very high. How do I resolve this problem?
    The process domain encountered the following errors while loading the process "myOrderBooking" (revision "1.0"): Failed to read wsdl.
    Failed to read wsdl at "http://127.0.0.1:9700/orabpel/default/CreditRatingService/CreditRatingService?wsdl", because "Failed to read WSDL from http://127.0.0.1:9700/orabpel/default/CreditRatingService/CreditRatingService?wsdl: HTTP connection error code is 502".
    Thanks,
    Ravi

    are you getting the HTTP 502 error?
    If so it looks like you have proxy issues getting out the external service. Either you are not going through a proxy service when one is required, or the traffic is being routed through a proxy server for an internal address.
    To try and solve it start a browser session on the server and test the URL. If successful configure the SOA proxy setting the same as the brower.
    cheers
    James

  • "HTTP500 - OTHER_ERROR: Failed to read WSDL" creating a Web Service in OBPM

    I'm currently experiencing a problem with OBPM 11g when trying to consume a Web service into my composite application.
    I have created a BPM Application and have previously been able to consume Web Services from our service bus. Since a recent restart of my client however, I can nolonger consume the same (or indeed any) service from any location as JDeveloper gives nme the following error when trying to access the WSDL file...
    Error while reading wsdl file
    http://<server>:<port>/<service>).wsdl
    Exception:
    WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from
    http://<server>:<port>/<service>).wsdl:
    HTTP Connection error code is 500
    I can navigate to the WSDL within IE on the same client and I have switched off the "Use HTTP Proxy Server" within the "Web Browser and Proxy" preferences'. Are there any other preferences or settings that could be causing this issue?
    Steps to reproduce...
    Open the cmpsite.xml view of the application
    Drag a Web service component from the Service Adapters within the SOA Componet pane
    Enter the name of the Service
    Paste the WSDL location into the WSDL URL
    Try to select port type
    At this point the error is received
    Thanks to anyone who can assist
    Darren
    Edited by: 784610 on 27-Jul-2010 02:32
    Edited by: 784610 on 27-Jul-2010 02:32

    Hi,
    I am facing the same issue while generating the client java class from IBM RAD 6.0.
    Here is the error I am getting.
    WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
         [java] at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
         [java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
         [java] at java.lang.Thread.run(Thread.java:571)
    Please guide me to resolve this issue.
    Thanks & Regards,
    Vijay

  • DCA-40002: Failed to read WSDL from xsd

    Hi,
    I am a newbie to JDeveloper, we are using Oracle JDeveloper 11g to consume a web service from PeopleSoft 9.0.
    We have a WSDL based on a PeopleSoft Component Interface. We can view the wsdl document through the PeopleSoftServiceListeningConnector URL and it appears ok.
    However, when we create a new Web Service Data Control in JDeveloper, it presents us with the following error:
    DCA-40002: The WSDL document is invalid due to the following reason: java.io.IOException: Failed to read WSDL from
    http://machine:port/PSIGW/PeopleSoftServiceListeningConnector/M999999.V1.xsd:
    HTTP connection error code is 500.
    Any advice would be appreciated.
    Thanks in advance.
    Regards,
    Dan

    Hi, after 1 1/2 years you can assume the thread to be closed. So please open your own thread and make sure the WSDL file is accessible from a browser URL.
    Frank

  • Failed to read wsdl file from url

    Hi all,
    I am struggling with WL 9.2, consuming a WSRP enabled portlet at the following point:
    Having created a proxy portlet, refering to the WSDL of the WSRP producer, I did successfully deploy the portal. When accessing the portal and consuming the portlet the following exception is thrown:
    com.bea.wsrp.faults.TransportException: Failed to read wsdl file from url due to -- java.net.ConnectException: Tried all: '8' addresses, but could not connect over HTTP to server: 'www.w3.org', port: '80';
    The WSDL includes a schema (http://www.w3.org/2001/XMLSchema). The URL is definetely accessible by the server.
    I am open for any kind of support ;) Thanks in advance!
    Kind regards,
    Matthias

    Yes, they are all local schemas. The way ALSB works, even if the import path in the wsdl or parent schema doesn't exist, relative to the current directory, you can specify which schema resolves that reference. My WSDL imports several schemas, all of which import others. When I was done importing all the schemas and resolving references, all the references in WSDLs and XSDs were assigned and valid. However, after all of those imports and reference resolution, it still says the WSDL is invalid, with the following odd error message:
    The WSDL is not semantically valid: Failed to read wsdl file from url due to -- java.net.MalformedURLException: no protocol: /XMLSchema/PaymentServices/Resources/PaymentServices-200802.
    That path listed refers to one of the schemas imported by the WSDL. The reference to that schema in the WSDL was resolved, and it doesn't complain about that reference.

  • Inside EM Console Test Service button-- Parse WSDL Failed to read WSDL

    Hi,
    I have SOA 11.1.1.5 installed. Have HTTPS setup also. I have multiple partitions and am facing an issue to access wsdls of all the processes deployed under that partition.
    In EM Console when I click any Process under the partition in question then click Test and get a screen whith a button Parse WSDL when I select that button
    I get the below error
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from
    https://host:port/soa-infra/services/SServices/ServiceFileList/ServiceFileList_client_ep?WSDL:WSDL not found
    at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157)
    at oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87)
    at oracle.sysman.emas.model.wsmgt.WSTestModel.init(WSTestModel.java:226)
    at oracle.sysman.emas.view.wsmgt.WSView.parseWSDL(WSView.java:166)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    ............................All the Processes deployed in other partitions works fine and can access the wsdl just fine it's only this one partition where I am facing the above issue.
    Any help is appreciated.
    Thanks

    Here are the steps I took so far but no luck
    I went ahead deleted the custom folder that holds all xsds, wsdls from MDS and re-imported into MDS.
    Undeployed all the processes and deleted the partition through EM.
    Logged into MDS and ran delete from MDS_PATHS where path_fullname like '/deployed-composites/CustomServices%';
    Again created the same partition through EM and deployed the Process but ran into the same issue.
    As all the processes deployed in this partition have there schemas stored in MDS and are not part of the Project. So looks like it's not able to access the MDS for the referenced objects and so the wsdl load fails. But even if I deploy any other simple process that doesn't refer to MDS this also doesn't load the wsdl but if deploy the same process in other partition it works fine so wondering if there's anything with the Partition even though I deleted and re-created but somewhere it still keeps something.
    But any process that refers MDS if deployed in any other partition also doesn't work.
    So facing 2 issues why anything deployed in that particular partition doesn't work and second why any process that reference MDS for any objects doesn't work regardless of which Partition it gets deployed.
    I really want to solve this rather than doing a complete reinstall which to me may endup in the same scenario.
    When a paste the wsdl url in a browser this is what I get
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding addressInside the EM when click Test->Parse WSDL I get the below error
    The WSDL document could not be parsed
    The following error occured while parsing the WSDL location -
    WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL
    from https://hostname/soa-infra/services/CustomServices/CustomServicesNotification/customserviceemailnotification_client_ep?WSDL:WSDL not found
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from https://hostname/soa-infra/services/CustomServices/CustomServicesNotification/customserviceemailnotification_client_ep?WSDL:WSDL not found
    oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:157) at
    oracle.sysman.emSDK.webservices.wsdlparser.ParsedWSDLFactoryImpl.getParsedWSDL(ParsedWSDLFactoryImpl.java:87) at
    As am not sure if this could be due to MDS or something is corrupted on the mid-tier.
    Any help is really appreciated.
    Thanks

Maybe you are looking for