BPEL Process Error calling WS

Hi, I'm following the SOADEMO quickstart tutorial, but it's really frustrating because in each step I always found missing things on the tutorial..
Please I'm very interested on this software but I cannot continue..
The error is the following:
[2007/04/25 10:41:13] Fallo al llamar a la operación "OrderSequence" en el proveedor "OrderSequence".menos
-<messages>
-<input>
-<orderSequenceInput>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="OrderSequenceInput_msg">
<OrderSequenceInput xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/OrderSequence"/>
</part>
</orderSequenceInput>
</input>
-<fault>
-<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>null
</code>
</part>
-<part name="summary">
<summary>
file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SOAOrderBooking_1.0_937b09d1bd8dae1b33b028b2871aef63.tmp/OrderSequence.wsdl [ OrderSequence_ptt::OrderSequence(OrderSequenceInput_msg,OrderSequenceOutputCollection) ] - WSIF JCA Execute of operation 'OrderSequence' failed due to: El marco del adaptador no ha podido crear la conexión de JCA saliente.
file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SOAOrderBooking_1.0_937b09d1bd8dae1b33b028b2871aef63.tmp/OrderSequence.wsdl [ OrderSequence_ptt::OrderSequence(OrderSequenceInput_msg,OrderSequenceOutputCollection) ] - : El marco del adaptador no ha podido establecer una conexión de JCA saliente debido al siguiente motivo: ORABPEL-12529
Problema de ManagedConnectionFactory.
No se ha podido instanciar ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory debido a:
     Falta la clase: oracle.tip.adapter.db.DBManagedConnectionFactory
     Clase Dependiente: oracle.tip.adapter.fw.wsdl.WSDLUtils
     Cargador: oracle.bpel.common:10.1.3
     Origen del Código: /C:/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
     Configuración: <code-source> in /C:/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
Esta carga se ha iniciado en orabpel.root:0.0.0 mediante el método Class.forName().
La clase que falta no está disponible desde ningún origen de código o cargador del sistema.
Asegúrese de que el adaptador de recursos JCA correspondiente se ha desplegado.
; nested exception is:
     ORABPEL-12511
El marco del adaptador no ha podido crear la conexión de JCA saliente.
file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SOAOrderBooking_1.0_937b09d1bd8dae1b33b028b2871aef63.tmp/OrderSequence.wsdl [ OrderSequence_ptt::OrderSequence(OrderSequenceInput_msg,OrderSequenceOutputCollection) ] - : El marco del adaptador no ha podido establecer una conexión de JCA saliente debido al siguiente motivo: ORABPEL-12529
Problema de ManagedConnectionFactory.
No se ha podido instanciar ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory debido a:
     Falta la clase: oracle.tip.adapter.db.DBManagedConnectionFactory
     Clase Dependiente: oracle.tip.adapter.fw.wsdl.WSDLUtils
     Cargador: oracle.bpel.common:10.1.3
     Origen del Código: /C:/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
     Configuración: <code-source> in /C:/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
Esta carga se ha iniciado en orabpel.root:0.0.0 mediante el método Class.forName().
La clase que falta no está disponible desde ningún origen de código o cargador del sistema.
Asegúrese de que el adaptador de recursos JCA correspondiente se ha desplegado.
Examine el archivo log en busca de motivos. Active el registro de depuración en la consola BPEL.
</summary>
</part>
-<part name="detail">
<detail>null
</detail>
</part>
</bindingFault>
</fault>
</messages>

There are two ways to check this:
- from the container, login to Oracle Enterprise Manager (<server>:<port>/em), find your OC4J instance where SOA Suite is running, then click the 'Administration' link. Then click the task icon at 'services', 'JDBC Resources'. Check the datasources there to see if they all point to the correct location.
- from JDeveloper, open the demo project. Double click the Database adapter(s) to see which connection is used. If you get an error, the connection probably isn't defined in JDeveloper. Click on the 'new..' button, and create a new database connection. The redeploy the project and try again.
HTH,
Bas

Similar Messages

  • Invoking Xai Service from  BPEL process (Error 411--Length Required)

    Hi Friends,
    I am trying to invoke xai inbound service webserive i.e WSDL from BPEL process, when i am testing the request i am getting the following error
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://190.12.19.100:6500/spl/XAIApp/xaiserver/CMMBC
    when i open the above end point url in the browser:
    Error 411--Length Required
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.12 411 Length Required
    The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
    pls help me out
    thanks and regards
    sivaram
    Edited by: sivaram on Apr 21, 2011 6:56 AM

    Yes we have got the same error while invoking from SOAP UI.
    But wsdl alone is opening through browser.
    But when we try opening the endpoint url we are getting the above error.
    Please help!

  • BPEL Process Errors at XML Gateway

    Hi
    I am in the process of developing AP Invoice Inbound process using BPEL.
    Process errored outs at XML Gateway with below error.
    The Standard:OAG, Transaction Type:AP , Transaction SubType:INI and Location Code 1 is not enabled in the XML Gateway Server. Pls check your Setup.
    I have gone through the XML Gateway setup but could not able to locate what exactly the problem.
    Could anybody help me out to fix this problem.
    Regards
    Kiran Akkiraju

    Hi,
    I am also experiencing the very same problem - does anyone have a solution for this or is this a bug?
    Thanks.
    Tony.

  • Pointing deployed BPEL process to call different version of another BPEL

    Hi All,
    I have deployed BPEL x calls BPEL y( version 1.0)
    Now I wanted to point BPEL x to BPEL y (version 2.0) and this should happen with out redeploying BPEL x
    I am okay to bounce server .
    Is there any solution ?
    Thansk,
    Praveen

    Guys why are you not understanding his question. I think he wrote quite clearly.
    He has 3 BPEL process deployed in version 1.0
    and
    have 2/3 BPEL deployed in version 2.0
    now what he wants is BEPL process with version 10.0 should always call 1.0 and the one with 2.0 always call 2.0. IS that too difficult to understand???
    Praven what i suggest as alternate for time till you get actual solution being is
    1. In version 2.0 before you deploy hard code partner links with version 2.0
    2. Deploy bpel with version 2.0
    3. Go and set version 1.0 of all bpel as default
    now since 1.0 are all default 1.0 will call 1.0
    in 2.0 since you hardcoded partnerlinks it will call 2.0
    in future don't mess thnsg up :)) and use dynamic binding.

  • Error while deploying BPEL Process(Error during deployment: Deployment Fail

    Hi,
    when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] HTTP error code returned [500]
    [04:53:50 PM] Error message from server:
    Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    [04:53:50 PM] Check server log for more details.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] #### Deployment incomplete. ####
    [04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Please, any one can tell solution for this.
    Thanks In advance
    Amar.
    Edited by: 897448 on Dec 13, 2011 8:48 PM

    Hi,
    when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] HTTP error code returned [500]
    [04:53:50 PM] Error message from server:
    Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    [04:53:50 PM] Check server log for more details.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] #### Deployment incomplete. ####
    [04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Please, any one can tell solution for this.
    Thanks In advance
    Amar.
    Edited by: 897448 on Dec 13, 2011 8:48 PM

  • ORABPEL-11811 - Error while calling PL/Sql API Into BPEL Process

    Hi,
    I have created a BPEL Process for creating a Order in Oracle using the synchronous process.
    I have followed the below steps.
    1) Created a Stored procedure using the Order Creation API's by passing Recard Type IN parameters.
    2) Created Synchronous BPEL Process and called the above Procedure using APPS Adapter.
    3) Created a xsd file and mapped the input and output parameter values using Transform Activity.
    After the above steps, when I try to run the BPEL process I am getting the below error:
    An error occurred while preparing and executing the APPS.PROC_PROC_NAME API. Cause: java.sql.SQLException: ORA-06531: Reference to uninitialized collection
    ORA-06512: at "APPS.PROC_PROC_NAME ", line 149
    ORA-06512: at line 1
    [Caused by: ORA-06531: Reference to uninitialized collection
    ORA-06512: at "APPS.PROC_NAME", line 149
    ORA-06512: at line 1
    ; nested exception is:
    ORABPEL-11811
    Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.PROC_PROC_NAME API. Cause: java.sql.SQLException: ORA-06531: Reference to uninitialized collection.
    Can anybody help in resolving the error?
    Thanks,
    Mastanvali.

    Here is the API Code..
    CREATE OR REPLACE PROCEDURE XXMAST_PRC(
    arg_in_p_header_rec           IN HeaderObject,
    arg_in_p_line_tbl          IN arrayLines,
    arg_out_x_return_status          OUT VARCHAR2,
    arg_out_order_number          OUT NUMBER,
    arg_out_header_id          OUT NUMBER,
    arg_out_flow_status_code     OUT VARCHAR2
    ) AS
         p_api_version_number          NUMBER;
         x_return_status      VARCHAR2(2);
         x_msg_count      NUMBER;
         x_msg_data      VARCHAR2(2000);
         v_msg_data               VARCHAR2(8000);
         v_msg_index_out               NUMBER(10);
         p_header_rec      OE_ORDER_PUB.HEADER_REC_TYPE;
         p_old_header_rec      OE_ORDER_PUB.HEADER_REC_TYPE;
         p_header_val_rec      OE_ORDER_PUB.Header_Val_Rec_Type;
         p_old_header_val_rec      OE_ORDER_PUB.Header_Val_Rec_Type;
         p_Header_Adj_tbl      OE_ORDER_PUB.Header_Adj_Tbl_Type;
         p_old_Header_Adj_tbl      OE_ORDER_PUB.Header_Adj_Tbl_Type;
         p_Header_Adj_val_tbl      OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
         p_old_Header_Adj_val_tbl      OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
         p_Header_price_Att_tbl      OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
         p_old_Header_Price_Att_tbl      OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
         p_Header_Adj_Att_tbl      OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
         p_old_Header_Adj_Att_tbl      OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
         p_Header_Adj_Assoc_tbl      OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
         p_old_Header_Adj_Assoc_tbl      OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
         p_Header_Scredit_tbl      OE_ORDER_PUB.Header_Scredit_Tbl_Type;
         p_old_Header_Scredit_tbl      OE_ORDER_PUB.Header_Scredit_Tbl_Type;
         p_Header_Scredit_val_tbl      OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
         p_old_Header_Scredit_val_tbl      OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
         p_line_tbl      OE_ORDER_PUB.Line_Tbl_Type;
         p_old_line_tbl      OE_ORDER_PUB.Line_Tbl_Type;
         p_line_val_tbl      OE_ORDER_PUB.Line_Val_Tbl_Type;
         p_old_line_val_tbl      OE_ORDER_PUB.Line_Val_Tbl_Type;
         p_Line_Adj_tbl      OE_ORDER_PUB.Line_Adj_Tbl_Type;
         p_old_Line_Adj_tbl      OE_ORDER_PUB.Line_Adj_Tbl_Type;
         p_Line_Adj_val_tbl      OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
         p_old_Line_Adj_val_tbl      OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
         p_Line_price_Att_tbl      OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
         p_old_Line_Price_Att_tbl      OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
         p_Line_Adj_Att_tbl      OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
         p_old_Line_Adj_Att_tbl      OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
         p_Line_Adj_Assoc_tbl      OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
         p_old_Line_Adj_Assoc_tbl      OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
         p_Line_Scredit_tbl      OE_ORDER_PUB.Line_Scredit_Tbl_Type;
         p_old_Line_Scredit_tbl      OE_ORDER_PUB.Line_Scredit_Tbl_Type;
         p_Line_Scredit_val_tbl      OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
         p_old_Line_Scredit_val_tbl      OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
         p_Lot_Serial_tbl      OE_ORDER_PUB.Lot_Serial_Tbl_Type;
         p_old_Lot_Serial_tbl      OE_ORDER_PUB.Lot_Serial_Tbl_Type;
         p_Lot_Serial_val_tbl      OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
         p_old_Lot_Serial_val_tbl      OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
         p_action_request_tbl      OE_ORDER_PUB.Request_Tbl_Type;
         x_header_rec OE_ORDER_PUB.Header_Rec_Type;
         x_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type;
         x_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
         x_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
         x_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
         x_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
         x_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
         x_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
         x_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type;
         x_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
         x_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
         x_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
         x_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
         x_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
         x_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
         x_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
         x_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
         x_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
         x_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type;
         x_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
         x_action_request_tbl     OE_ORDER_PUB.Request_Tbl_Type;
         icount                    NUMBER :=0;
    BEGIN
         fnd_global.apps_initialize(1318,21623,660);
         fnd_client_info.set_org_context(204);
         p_header_rec:= OE_ORDER_PUB.G_MISS_HEADER_REC;
         SELECT OE_ORDER_HEADERS_S.NEXTVAL INTO p_header_rec.header_id FROM DUAL;
         dbms_output.put_line('Header ID          = '|| p_header_rec.header_id);
         p_api_version_number := 1.0;
    ------------------------------------------header code-----------------------------------------------------------------------
              p_header_rec.order_type_id          := arg_in_p_header_rec.order_type_id;
              p_header_rec.sold_to_org_id          := arg_in_p_header_rec.sold_to_org_id;
              p_header_rec.ship_to_org_id          := arg_in_p_header_rec.ship_to_org_id;
              p_header_rec.transactional_curr_code:= arg_in_p_header_rec.transactional_curr_code;
              p_header_rec.order_source_id          := arg_in_p_header_rec.order_source_id;
              p_header_rec.org_id               := arg_in_p_header_rec.org_id;
              p_header_rec.ship_from_org_id          := arg_in_p_header_rec.ship_from_org_id;
              p_header_rec.payment_term_id           := arg_in_p_header_rec.payment_term_id;
              p_header_rec.price_list_id          := 1000;
              p_header_rec.freight_terms_code          := 'Due';     -- Prepay and Add
              p_header_rec.operation               := OE_GLOBALS.G_OPR_CREATE;
              p_header_rec.pricing_date          := SYSDATE;
              p_header_rec.creation_date          := SYSDATE;
              p_header_rec.booked_flag          := 'N';
              p_header_rec.created_by               := 1318;
              p_header_rec.last_updated_by          := 1318;
              p_header_rec.last_update_date          := SYSDATE;
              p_header_rec.invoice_to_org_id          := 1424;
              p_header_rec.version_number          := 1;
              p_header_rec.open_flag               := 'Y';
              p_header_rec.ordered_date          := SYSDATE;
              p_header_rec.flow_status_code          := 'ENTERED';
              p_header_rec.tax_exempt_flag          := 'S';
              p_header_rec.salesrep_id          := -3;
    --------------------------------------------LINES CODE------------------------------------------------------------
         icount := 0;
         for icount in 1 .. arg_in_p_line_tbl.count loop
              p_line_tbl(icount) := Oe_Order_Pub.G_MISS_LINE_REC;
              SELECT OE_ORDER_LINES_S.NEXTVAL INTO p_line_tbl(icount).line_id FROM DUAL;
              dbms_output.put_line('Line ID               = '|| p_line_tbl(icount).line_id);
         p_line_tbl(icount).inventory_item_id          := arg_in_p_line_tbl(icount).inventory_item_id;
         p_line_tbl(icount).ordered_quantity          := arg_in_p_line_tbl(icount).ordered_quantity;
         p_line_tbl(icount).pricing_quantity          := arg_in_p_line_tbl(icount).pricing_quantity;
         p_line_tbl(icount).line_type_id               := arg_in_p_line_tbl(icount).line_type_id;
         p_line_tbl(icount).line_number          := icount;
         p_line_tbl(icount).shipment_number          := arg_in_p_line_tbl(icount).shipment_number;
         p_line_tbl(icount).ship_to_org_id          := arg_in_p_line_tbl(icount).ship_to_org_id;
         p_line_tbl(icount).sold_to_org_id          := arg_in_p_line_tbl(icount).sold_to_org_id;
         p_line_tbl(icount).salesrep_id          := arg_in_p_line_tbl(icount).salesrep_id;
         p_line_tbl(icount).payment_term_id          := arg_in_p_line_tbl(icount).payment_term_id;
              p_line_tbl(icount).price_list_id          := 1000;
              p_line_tbl(icount).operation               := OE_GLOBALS.G_OPR_CREATE;
              p_line_tbl(icount).open_flag               := 'Y';
              p_line_tbl(icount).booked_flag               := 'N';
              p_line_tbl(icount).header_id               := p_header_rec.header_id;
              p_line_tbl(icount).line_category_code          := 'ORDER';
              p_line_tbl(icount).order_quantity_uom          :='Ea';
              p_line_tbl(icount).request_date               := SYSDATE;
              p_line_tbl(icount).schedule_ship_date          := SYSDATE;
              p_line_tbl(icount).ship_from_org_id          := 204;
              p_line_tbl(icount).flow_status_code          := 'ENTERED';
              p_line_tbl(icount).ship_to_customer_id          := 1290;
              p_line_tbl(icount).invoice_to_org_id          := 1424;
              p_line_tbl(icount).tax_exempt_flag          := 'S';
              p_line_tbl(icount).tax_date               := '02-Mar-2005';
              p_line_tbl(icount).tax_code               := 'Location';
              SELECT OE_PRICE_ADJUSTMENTS_S.NEXTVAL INTO p_Line_Adj_tbl(icount).price_adjustment_id FROM DUAL;
              dbms_output.put_line('Price Adjustment ID     = '|| p_Line_Adj_tbl(icount).price_adjustment_id);
              p_Line_Adj_tbl(icount).created_by          := 1318;
              p_Line_Adj_tbl(icount).header_id          := p_header_rec.header_id;
              p_Line_Adj_tbl(icount).line_id               := p_line_tbl(icount).line_id;
              p_Line_Adj_tbl(icount).percent               := 10;
              p_Line_Adj_tbl(icount).operation          := OE_GLOBALS.G_OPR_CREATE;
              p_Line_Adj_tbl(icount).list_header_id          := 8988;
              p_Line_Adj_tbl(icount).list_line_id          := 16596;
              p_Line_Adj_tbl(icount).list_line_type_code     := 'DIS';
              p_Line_Adj_tbl(icount).arithmetic_operator     := 'AMT';
              p_Line_Adj_tbl(icount).updated_flag          := 'Y';
              p_Line_Adj_tbl(icount).update_allowed          := 'Y';
              p_Line_Adj_tbl(icount).applied_flag          := 'Y';
              p_Line_Adj_tbl(icount).automatic_flag          := 'N';
              p_Line_Adj_tbl(icount).OPERAND               := 10;
         end loop;
         oe_msg_pub.initialize;
         oe_order_pub.process_order
              ( p_api_version_number =>      p_api_version_number
              , p_init_msg_list =>      FND_API.G_FALSE
              , p_return_values =>      FND_API.G_FALSE
              , p_action_commit =>      FND_API.G_FALSE
              , x_return_status =>      x_return_status
              , x_msg_count =>      x_msg_count
              , x_msg_data =>      x_msg_data
              , p_header_rec =>     p_header_rec
              , p_old_header_rec =>     p_old_header_rec
              , p_header_val_rec =>     p_header_val_rec
              , p_old_header_val_rec =>     p_old_header_val_rec
              , p_Header_Adj_tbl =>     p_Header_Adj_tbl
              , p_old_Header_Adj_tbl =>     p_old_Header_Adj_tbl
              , p_Header_Adj_val_tbl =>     p_Header_Adj_val_tbl
              , p_old_Header_Adj_val_tbl =>     p_old_Header_Adj_val_tbl
              , p_Header_price_Att_tbl =>     p_Header_price_Att_tbl
              , p_old_Header_Price_Att_tbl =>     p_old_Header_Price_Att_tbl
              , p_Header_Adj_Att_tbl =>     p_Header_Adj_Att_tbl
              , p_old_Header_Adj_Att_tbl =>      p_old_Header_Adj_Att_tbl
              , p_Header_Adj_Assoc_tbl =>     p_Header_Adj_Assoc_tbl
              , p_old_Header_Adj_Assoc_tbl =>      p_old_Header_Adj_Assoc_tbl
              , p_Header_Scredit_tbl =>     p_Header_Scredit_tbl
              , p_old_Header_Scredit_tbl =>     p_old_Header_Scredit_tbl
              , p_Header_Scredit_val_tbl =>     p_Header_Scredit_val_tbl
              , p_old_Header_Scredit_val_tbl =>     p_old_Header_Scredit_val_tbl
              , p_line_tbl =>     p_line_tbl
              , p_old_line_tbl =>     p_old_line_tbl
              , p_line_val_tbl =>     p_line_val_tbl
              , p_old_line_val_tbl =>     p_old_line_val_tbl
              , p_Line_Adj_tbl =>     p_Line_Adj_tbl
              , p_old_Line_Adj_tbl =>     p_old_Line_Adj_tbl
              , p_Line_Adj_val_tbl =>     p_Line_Adj_val_tbl
              , p_old_Line_Adj_val_tbl =>     p_old_Line_Adj_val_tbl
              , p_Line_price_Att_tbl =>     p_Line_price_Att_tbl
              , p_old_Line_Price_Att_tbl =>     p_old_Line_Price_Att_tbl
              , p_Line_Adj_Att_tbl =>     p_Line_Adj_Att_tbl
              , p_old_Line_Adj_Att_tbl =>      p_old_Line_Adj_Att_tbl
              , p_Line_Adj_Assoc_tbl =>     p_Line_Adj_Assoc_tbl
              , p_old_Line_Adj_Assoc_tbl =>      p_old_Line_Adj_Assoc_tbl
              , p_Line_Scredit_tbl =>     p_Line_Scredit_tbl
              , p_old_Line_Scredit_tbl =>     p_old_Line_Scredit_tbl
              , p_Line_Scredit_val_tbl =>     p_Line_Scredit_val_tbl
              , p_old_Line_Scredit_val_tbl =>     p_old_Line_Scredit_val_tbl
              , p_Lot_Serial_tbl =>     p_Lot_Serial_tbl
              , p_old_Lot_Serial_tbl =>     p_old_Lot_Serial_tbl
              , p_Lot_Serial_val_tbl =>     p_Lot_Serial_val_tbl
              , p_old_Lot_Serial_val_tbl =>     p_old_Lot_Serial_val_tbl
              , p_action_request_tbl =>     p_action_request_tbl
              , x_header_rec =>      x_header_rec
              , x_header_val_rec =>      x_header_val_rec
              , x_Header_Adj_tbl =>      x_Header_Adj_tbl
              , x_Header_Adj_val_tbl =>      x_Header_Adj_val_tbl
              , x_Header_price_Att_tbl =>      x_Header_price_Att_tbl
              , x_Header_Adj_Att_tbl =>      x_Header_Adj_Att_tbl
              , x_Header_Adj_Assoc_tbl =>      x_Header_Adj_Assoc_tbl
              , x_Header_Scredit_tbl =>      x_Header_Scredit_tbl
              , x_Header_Scredit_val_tbl =>      x_Header_Scredit_val_tbl
              , x_line_tbl =>      x_line_tbl
              , x_line_val_tbl =>      x_line_val_tbl
              , x_Line_Adj_tbl =>      x_Line_Adj_tbl
              , x_Line_Adj_val_tbl =>      x_Line_Adj_val_tbl
              , x_Line_price_Att_tbl =>      x_Line_price_Att_tbl
              , x_Line_Adj_Att_tbl =>      x_Line_Adj_Att_tbl
              , x_Line_Adj_Assoc_tbl =>      x_Line_Adj_Assoc_tbl
              , x_Line_Scredit_tbl =>      x_Line_Scredit_tbl
              , x_Line_Scredit_val_tbl =>      x_Line_Scredit_val_tbl
              , x_Lot_Serial_tbl =>      x_Lot_Serial_tbl
              , x_Lot_Serial_val_tbl =>      x_Lot_Serial_val_tbl
              , x_action_request_tbl     =>      x_action_request_tbl
         IF (x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
              COMMIT;
         dbms_output.put_line('Return Status - '|| SUBSTR (x_return_status,1,255));
         dbms_output.put_line('------------------------------------');
         dbms_output.put_line('Order Number ==== '|| x_header_rec.order_number);
         dbms_output.put_line('------------------------------------');
              arg_out_x_return_status := x_return_status;
              arg_out_order_number          := x_header_rec.order_number;
              arg_out_header_id          := p_header_rec.header_id;
              arg_out_flow_status_code     := p_header_rec.flow_status_code;
         ELSE
              dbms_output.put_line('Return Status = '|| SUBSTR (x_return_status,1,255));
              dbms_output.put_line('Msg Count = '|| TO_CHAR(x_msg_count));
              dbms_output.put_line('Msg Data = '|| SUBSTR (x_msg_data,1,255));
              IF x_msg_count >1 THEN
                   FOR I IN 1..x_msg_count LOOP
                        Oe_Msg_Pub.get(
                             p_msg_index           => i
                             ,p_encoded           => Fnd_Api.G_FALSE
                             ,p_data           => v_msg_data
                             ,p_msg_index_out      => v_msg_index_out
                        DBMS_OUTPUT.PUT_LINE('v_msg_index_out '|| v_msg_index_out);
                        DBMS_OUTPUT.PUT_LINE('v_msg_data '|| v_msg_data);
                   END LOOP;
              END IF;
         END IF;
    END;
    /

  • New problem calling PL/SQL based WS from BPEL process

    I have created a webservice based on a PL/SQL package based function with JDeveloper and deployed the web service on the BPEL OC4J server.
    Calling the web service endpoint directly from internet explorer works fine.
    I have also created and deployed a BPEL process to call this web service. When i run the process it completes normally but returns an Oracle error in the out-variable: "Ora-06502 Numerical value error".
    Through my PL/SQL logging i can see that the input-variable to the PL/SQL function is empty (so when i try to use this value it gives me the Ora-06502 error).
    When i check the audit trail of the BPEL process instance i find that the assignment of the input variable is ok. This input variable is used in the invokation of the web service (and at this point still has the proper value).
    What can be wrong? (the only part i cannot trace is the working of the Java stub created by JDeveloper).
    Any ideas?
    thanks, Bart

    This is the complete stack trace:
    <2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: CataLog
    <2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> inputContainer: {InputParameters=<CATLOG xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/EBILLING/CATALOG/"><ID_AZIENDA>134</ID_AZIENDA><ID_PROGETTO>134</ID_PROGETTO><CAPTURE_DATETIME>1959</CAPTURE_DATETIME><FULLNAME>lkjh</FULLNAME><PATHNAME>kjsf</PATHNAME><FILENAME>kjsf</FILENAME><DESTINATION_PATH>kjsf</DESTINATION_PATH><MOVE_DATETIME>1959</MOVE_DATETIME><SIZE_BYTES>134</SIZE_BYTES><LAST_WRITE>1959</LAST_WRITE><ID_THOR>2345234</ID_THOR><SNAPSHOT_PATH>kjsf</SNAPSHOT_PATH></CATLOG>}
    <2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> callProps: {is-initial-call=true, parentId=5602, process-id=StoredProcedure, rootId=5602, conversationId=bpel://localhost/default/StoredProcedure~1.0/5602-BpInv0-BpSeq0.3-3, location=null, priority=0, work-item-key=5602-BpInv0-BpSeq0.3-3, domain-id=default, revision-tag=1.0}
    <2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl
    <2004-12-01 10:48:52,014> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=CataLogportTypeQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_pttserviceQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog
    <2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[{http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_ptt]: Locating jndiAdapterInstance eis/CatapultDBLog
    <2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
    <2004-12-01 10:48:52,016> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
    <2004-12-01 10:48:52,234> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
    <2004-12-01 10:48:52,235> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
    <2004-12-01 10:48:52,294> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Invoking JCA outbound Interaction
    <2004-12-01 10:48:52,296> <DEBUG> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
    <2004-12-01 10:48:52,297> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    <2004-12-01 10:48:52,299> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    ... 27 more
    java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    <2004-12-01 10:48:52,300> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happenned
    ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    ... 27 more
    <2004-12-01 10:48:52,302> <DEBUG> <default.collaxa.cube.ws> <BPELInvokeWMP::__invoke> Caught RemoteException
    orabpel.apache.wsif.WSIFException: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA@788a7bhttp://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] : Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    ; nested exception is:
    ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:464)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    ... 25 more
    Caused by: java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    ... 27 more

  • How to design BPEL process where BPEL is called by PL/SQL code?

    Hi,
    My BPEL process is called by a PL/SQL code given below.
    CREATE OR REPLACE PROCEDURE testd(errbuf OUT VARCHAR2,
    retcode OUT VARCHAR2)
    IS
    soap_request VARCHAR2(20000);
    soap_respond VARCHAR2(10000);
    http_req UTL_HTTP.REQ;
    http_resp UTL_HTTP.RESP;
    l_detail VARCHAR2(10000);
    endpoint VARCHAR2(130);
    begin
    endpoint := 'http://afsmlnx04.rheem.com:7105/soa-infra/services/default/HelloWorldPayload/bpelprocess1_client_ep';
    soap_request := '<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body xmlns:ns1="http://oracle.nl/HelloWorldPayload"><ns1:process><ns1:input>abc</ns1:input></ns1:process></soap:Body></soap:Envelope>';
    http_req := utl_http.begin_request(
    endpoint
    , 'POST'
    , 'HTTP/1.1'
    utl_http.set_header(http_req
    , 'Content-Type'
    , 'text/xml');
    utl_http.set_header(http_req
    , 'Content-Length'
    , length(soap_request));
    utl_http.set_header(http_req
    , 'SOAPAction'
    , 'process');
    utl_http.write_text(http_req, soap_request);
    http_resp := utl_http.get_response(http_req);
    utl_http.read_text(http_resp, soap_respond);
    utl_http.end_response(http_resp);
    dbms_output.put_line('soap'||soap_respond);
    EXCEPTION
    WHEN utl_http.end_of_body THEN
    utl_http.end_response(http_resp);
    WHEN utl_http.request_failed THEN
    DBMS_OUTPUT.PUT_LINE('Request Failed: ' || utl_http.get_detailed_sqlerrm);
    WHEN utl_http.http_server_error THEN
    DBMS_OUTPUT.PUT_LINE('Server Error: ' || utl_http.get_detailed_sqlerrm);
    WHEN utl_http.http_client_error THEN
    DBMS_OUTPUT.PUT_LINE('Client Error: ' || utl_http.get_detailed_sqlerrm);
    WHEN others THEN
    DBMS_OUTPUT.PUT_LINE(sqlerrm);
    END;
    The above procedure will be defined as concurrent program in Oracle EBS.This concurrent program will call the bpel process.My question is how should i design the bpel process so that bpel will know it is called by a concurrent program?
    My BPEL is doing picking a file by FTP adapter and inserting data into a table.
    Please throw some lights on this!!

    Option 1:
    You have to design the service as a synchronous BPEL process
    1. Do a synchronous ftp get to read the file.
    2. Transform and write it into database table
    3. Reply results back to plsql
    Disadvantage: Your BPEL process should complete from BPEL timeout happens.
    Option 2:
    1. Enqueue the message into AQ from the concurrent program
    2. From the BPEL monitor the AQ, start the process when the message arrives
    3. Do a synchronous ftp get to read the file.
    4. Transform and write it into database table
    You cannot reply the results back to concurrent program.
    5. However, you could have another AQ to send the results back to concurrent program.
    6. Your concurrent program should listen to the resultsAQ to get the results back from BPEL.
    Option 2 is a relliable design.
    --Prasanna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Call to BPEL Process from JSP - Not working!

    Hi All,
    I'm trying to execute the sample JSP page provided in the BPEL Guide, which calls the BPEL "CreditRatingService" service.
    The JSP Page compiled normally, but it does not invoke the BPEL Process. The JSP Page is just waiting.. the browser is loading the page for ever..which means it is not able to call the BPEL process. If i comment the below code
    NormalizedMessage res = deliveryService.request("CreditRatingService", "process", nm);
    then the page is displaying..
    Thanks for any help
    Regards
    Chandra

    Hi Afonso,
    I looked at the files under the below locations..
    C:\product\10.1.3.1\OracleAS_1\j2ee\home\log\home_default_group_1
    C:\product\10.1.3.1\OracleAS_1\bpel\system\logs
    C:\product\10.1.3.1\OracleAS_1\bpel\domains\default\logs
    I found the below error mesage
    <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http:.........
    from C:\product\10.1.3.1\OracleAS_1\bpel\system\logs\orabpel.txt log file.
    But this log file is generated when I start my SOA Suite and not when I open the JSP Page. But I'm guessing may be for the same reason, it the not calling the BPEL process.
    I don't have any issues while I deploy the BPEL process or calling the BPEL Process from the console.
    Thanks for any help
    -Chandra

  • Error in deploying my BPEL process

    I am getting the following error while I tried to deploy my BPEL process:
    Error:
    [Error ORABPEL-10902]: compilation failed
    [Description]: in "bpel.xml", XML parsing failed because "undefined part element.
    In WSDL at "file:/D:/projects/MyBPEL/bpel/MySvc-v1.wsdl", message part element "{http://www.company.com/wsdl/MySvc-v1.0}GeneralFault" is not defined in any of the schemas.
    Please make sure the spelling of the element QName is correct and the WSDL import is complete.
    [Potential fix]: n/a.
    I do not understand the error. 'GeneralFault' is defined in MySvc-v1.wsdl and not in a separate xsd.
    Here is a portion of MySvc-v1.wsdl:
    <?xml version="1.0" encoding="utf-8"?>
    <wsdl:definitions name="MySvc-v1.wsdl"
         xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
         xmlns="http://schemas.xmlsoap.org/wsdl/"
         xmlns:tns="http://www.company.com/wsdl/MySvc-v1"
         xmlns:v1_0="http://www.company.com/wsdl/MySvc-v1.0"
         xmlns:base="http://www.company.com/xsd/Base"
         targetNamespace="http://www.company.com/wsdl/MySvc-v1">
    <wsdl:types>
         <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
         targetNamespace="http://www.company.com/wsdl/MySvc-v1.0">
              <xsd:import schemaLocation="../xsd/Base.xsd" namespace="http://www.company.com/xsd/Base" />
              <xsd:element name="MyRq">
                   <xsd:complexType>
                   <xsd:sequence>
                        <xsd:element ref="base:ID" />
                        <xsd:element ref="base:SSN" />
                   </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="MyRs">
                   <xsd:complexType>
                   <xsd:sequence>
                        <xsd:element ref="base:Result" />
                        <xsd:element name="Timestamp" type="xsd:string"/>
                   </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="GeneralFault" type="xsd:string" />
         </xsd:schema>
    </wsdl:types>
    <wsdl:message name="MyRequest">
    <wsdl:part name="In" element="v1_0:MyRq" />
    </wsdl:message>
    <wsdl:message name="MyResponse">
    <wsdl:part name="Out" element="v1_0:MyRs" />
    </wsdl:message>
    <wsdl:message name="fault">
    <wsdl:part name="fault" element="v1_0:GeneralFault" />
    </wsdl:message>
    Thanks,
    AJ

    So does anyone know why I m getting the following error when the definition of "GeneralFault" is in the .wsdl file? According to the error messge, it sounds like I have to define it in a .xsd file.
    Error ORABPEL-10902: compilation failed
    Description: in "bpel.xml", XML parsing failed because "undefined part element.
    In WSDL at "file:/D:/projects/MyBPEL/bpel/MySvc-v1.wsdl", message part element "{http://www.company.com/wsdl/MySvc-v1.0}GeneralFault" is not defined in any of the schemas.
    Please make sure the spelling of the element QName is correct and the WSDL import is complete
    AJ

  • Unable to deploy BPEL Process --  Says If you have installed a patch to the

    I have a simple BPEL process that calles an ESB flow deployed in the same server.
    I am facing the following issue when trying to deploy the BPEL process.
    The ESB flow is deployed and is working perfectly.
    Configuration:
    JDeveloper 10.1.3.5
    SOA Suite 10g Release 3
    Downloaded from:
    http://www.oracle.com/technetwork/middleware/ias/downloads/index.html
    Here I downloaded this file:
    http://download.oracle.com/otn/nt/ias/101310/soa_windows_x86_101310_disk1.zip
    When I compile the BPEL project, it compiles fine:
    Compiling...
    Compiling C:\JDeveloper\10gMywork\OrderProcessingApp\OrderDistributionProcess\bpel\OrderDistributionProcess.bpel
    *[BPEL Compiler] Initializing compiler for first time use...*
    BPEL suitcase generated in: C:\JDeveloper\10gMywork\OrderProcessingApp\OrderDistributionProcess\output\bpel_OrderDistributionProcess_v2011_09_01__39889.jar
    copying bpel/OrderDistributionProcess.wsdl to output directory
    copying bpel/OrderSystem_OrderSearchService_RSRef.wsdl to output directory
    converting, through native2ascii, build.properties to output directory
    *[11:05:04 AM] Successful compilation: 0 errors, 0 warnings.*
    Now when I choose (Right Click on Project) -> Deploy -> BPEL Process Deployer,
    I get this error:
    Buildfile: C:\JDeveloper\10gMywork\OrderProcessingApp\OrderDistributionProcess\build.xml
    [java] Java Result: 1
    validateTask:
    [echo]
    | Validating workflow
    [validateTask] Validation of workflow task definitions is completed without errors
    deployProcess:
    [echo]
    | Deploying bpel process OrderDistributionProcess on localhost, port 8888
    [deployProcess] Deploying process C:\JDeveloper\10gMywork\OrderProcessingApp\OrderDistributionProcess\output\bpel_OrderDistributionProcess_1.0.jar
    BUILD FAILED
    C:\JDeveloper\10gMywork\OrderProcessingApp\OrderDistributionProcess\build.xml:78: A problem occured while connecting to server "localhost" using port "8888": bpel_OrderDistributionProcess_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 "OrderDistributionProcess" (revision "1.0"): null.
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:285)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:804)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:670)
    at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:445)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
    at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:317)
    at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:339)
    at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
    at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Total time: 6 seconds
    I checked the host port, i.e., 8888 here, from JDeveloper; and it says that the tests passed.
    Help me please.

    Balu,
    it seems you are trying to deploy example for B2B. Please check your B2B is up, AQ are up and accessible and you can also check your SOA dehydration DB .
    You can check some setup and dexample at: http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TU_001_B2B_BPEL.pdf
    -JMehta

  • BPEL process crashes randomly

    Iam working on softwareproject based on JAVA Web Services, deployed on a AXIS server, which are orchestrated in a BPEL process. The BPEL process was created with JDeveloper and deployed on the Oracle BPEL PM 10.1.3.1.0.
    The main WMYPC BPEL process invokes several other BPEL processes, which represent functionality of lower layers. The lower BPEL processes invoke again lower BPEL processes. So there exist three layers of BPEL process.
    Each BPEL process was tested and worked correctly, but when the main BPEL process is called, which involves the other BPEL processes, the main process crashs randomly on different stages of progress, after a lower process is getting invoked with the following error message:
    Your test request was processed synchronously. It took 83.464seconds to finish and generated the following output:
    Value:      
    <Faulthttp://schemas.xmlsoap.org/soap/envelope/>
    <faultcode>env:Server</faultcode>
    <faultstring>java.lang.IllegalStateException: Cannot call setRollbackOnly() current thread is NOT associated with a transaction</faultstring>
    </Fault>
    Beside the error above, a second error occures sometimes.
    Your test request was processed synchronously. It took 64.891seconds to finish and generated the following output:
    Value:      
    <Faulthttp://schemas.xmlsoap.org/soap/envelope/>
    <faultcode>env:Server</faultcode>
    <faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 70976ad86304fa5b:-18ed62ca:111af3d9f30:-7ff0. Please check the process instance for detail.</faultstring>
    </Fault>
    The development enviroment runs on a virtual machine running MS Windows Server 2003 SP1 with performance problems. So i thought there is a timeout problem and changed the syncMaxWaitTime for the BPEL domain to 120, but i didnt saw any improvements.
    I guess its a PM configuration problem and hope somebody can help me to solve it.
    Thanks for your help in advance.
    Regards Ronbee
    Message was edited by:
    ronbee

    Hi Ronbee,
    I guess you are using VMWare for Windows 2003 Server.
    If that's the case , then its an obvious performance issue.
    Cheers
    Anirudh Pucha

  • Querying BPEL process and sub-processes

    Hi there,
    I am new to BPEL and in our BPEL process we are calling like 5 other BPEL sub-processes. So assume our BPEL process A calls processes B, C, D, E, and F. Now for our fault handing if for example processes D fails I would like to retire sub-processes A but also sub-process B, C and D.
    Can anyone tell me which API would give me this information? Kind of like the tree in the BPEL console where we can see all the child processes.
    Thanks.

    Eric,
    No for us we have a generic BPEL error handling process where we are dynamically retiring the calling process. I got the Java API to dynamically retire the main calling process. But my main goal is to retire all the sub process that the main calling process calls as well.
    I looked at Matt Wright's Blog : tracing sub process calls within BPEL. He says you can use programatically for each instance one could query using the track of a parent id and root id but I need to get the details on how would I use the API. If you or anyone has that information can you please share that with me. Would really appreciate it.
    Thanks

  • What is the best way to capture exceptions raised by BPEL process?

    We have a BPEL process that calls an EBusiness Suite public pl/sql API. (For ex. setting and releasing holds on a Sales Order). And the API provides out parameters that will contain sql errors raised if any. What should I do to capture this error and show it on BAM? Or is there a better way of exposing this message to a particular user?

    Why couldn't you take the output and test if there are results and then use a switch statement to detemine what to do with these results.

  • BPEL Compilation Error: Load of wsdl "with Message part element undefined..

    Hi Friends,
    I am getting following error while compiling my BPEL process:
    Error: Load of wsdl "FTPWrite.wsdl with Message part element undefined in wsdl [file:/D:/MyData/_MyProjects/052_Amazon_MetadataInterface/001_SVN/002_Intl/trunc/MetadataInterfaceIntl_2013Apr15_WorkingCode/MetadataInterface_Intl/MetadataInterface_Intl.wsdl] part name = reply     type = {http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types}processResponse" failed
    However the reply message is already defined in the MetadataInterface_Intl.wsdlas shown below:
    Code for MetadataInterface_Intl.wsdl::::
    "<?xml version= '1.0' encoding= 'UTF-8' ?>
    <wsdl:definitions
    name="MetadataInterface_Intl"
    targetNamespace="http://xmlns.oracle.com/MetadataInterfaceIntl/MetadataInterface_Intl/MetadataInterface_Intl"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:inp1="http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types"
    xmlns:tns="http://xmlns.oracle.com/MetadataInterfaceIntl/MetadataInterface_Intl/MetadataInterface_Intl"
    >
    <wsdl:types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:import namespace="http://com.fox.metadata/MetadataInterfaceIntl/MetadataInterface_Intl/types" schemaLocation="xsd/Metadata_Interface.xsd"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="requestMessage">
    <wsdl:part name="request" element="inp1:process"/>
    </wsdl:message>
    *<wsdl:message name="replyMessage">*
    *<wsdl:part name="reply" element="inp1:processResponse"/>*
    *</wsdl:message>*
    <wsdl:portType name="execute_ptt">
    <wsdl:operation name="execute">
    <wsdl:input message="tns:requestMessage"/>
    <wsdl:output message="tns:replyMessage"/>
    </wsdl:operation>
    </wsdl:portType>
    </wsdl:definitions>"
    Surprisingly, this same code was compiling file last week and now I have no clue why I am getting this error. Can someone please shade some light on this issue?
    Thanks,
    Sachin.

    Hello
    I have had the same problem in Oracle BPM and solved it using the following steps:
    1- In your application navigator window, expand the project that contains the business rule.
    2- In the SOA Content, double click on your wsdl file.
    3- When the file opens, select the schema view from the bottom of the page.
    4- In the schema view, expand all the schema nodes and check if you see any values in red. If you see one, that value has probably caused the error and you should correct it using the property inspector window.
    In my case, the schema location value was set to a wrong path, so I changed it and the error resolved.
    Also, some error that appear as warning in the rule editor will show as compile error later, such as input types not being used and such, so those must be resolved before compiling.
    Hope that was helpful
    good luck

Maybe you are looking for