Error related to namespace mismatch in BPEL

Hi All
We are facing an error related to NameSpace of a variable in BPEL process.
We are sending a SOAP XML request to a third-party web service and fetching the XML response in a variable. There is a mismatch in the namespace of the variables. The xml response is having ‘ns1:’ while the variable created in BPEL process is having ‘ns23:’. Thus the process is giving the following error when initiated:
<part name="code" >
<code>Server.userException</code>
</part>
<part name="summary" >
<summary>when invoking endpointAddress 'https://cservice1.hrapply.com/WS/erp/ERPService', org.xml.sax.SAXParseException: The prefix "ns1" for element "ns1:newHireResponse" is not bound.</summary>
</part>
Complete error message is attached. We tried to rename the variable by changing the namespace in <process>.bpel file but that did not solve the issue. We have also tried to create a new process where the namespace given to the new output variable is ns1: But still he error persists.
Any pointer/suggestion to solve this issue is highly appreciated.
PS: We are using BPEL: 10.1.2.0.2

java.lang.ClassNotFoundException: org.springframework.web.servlet.DispatcherServletYou don't know how to solve class not found errors? That's incredibly basic Java classpath stuff that you not only should know, you MUST know how to handle before you can even think about touching a web environment. You are lacking some really basic core Java knowledge here. Are you perhaps trying to learn Java by diving right into a web application? If so - you can give up now, you have to start from the beginning and that is learn Java. Not only the language, the platform and the tools too.

Similar Messages

  • Namespace mismatch exception with Axis2

    Hi folks,
    I am getting the following exception when trying to invoke my axis2 web service,
    org.apache.axis2.AxisFault: namespace mismatch require http://services.sel.com found
         at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
         at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
         at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
         at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
         at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
         at com.sel.services.Invoker.main(Invoker.java:77)My wsdl is as follows,
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:ns="http://services.sel.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://services.sel.com">
        <wsdl:types>
            <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://services.sel.com">
                <xs:element name="echoMessage">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element minOccurs="0" name="name" nillable="true" type="xs:string"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>
                <xs:element name="echoMessageResponse">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element minOccurs="0" name="return" type="xs:boolean"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>
                <xs:element name="sayBye">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element minOccurs="0" name="name" nillable="true" type="xs:string"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>
                <xs:element name="sayByeResponse">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>
                <xs:element name="sayHi">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element minOccurs="0" name="name" nillable="true" type="xs:string"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>
                <xs:element name="sayHiResponse">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>
            </xs:schema>
        </wsdl:types>
        <wsdl:message name="echoMessageRequest">
            <wsdl:part name="parameters" element="ns:echoMessage"/>
        </wsdl:message>
        <wsdl:message name="echoMessageResponse">
            <wsdl:part name="parameters" element="ns:echoMessageResponse"/>
        </wsdl:message>
        <wsdl:message name="sayHiRequest">
            <wsdl:part name="parameters" element="ns:sayHi"/>
        </wsdl:message>
        <wsdl:message name="sayHiResponse">
            <wsdl:part name="parameters" element="ns:sayHiResponse"/>
        </wsdl:message>
        <wsdl:message name="sayByeRequest">
            <wsdl:part name="parameters" element="ns:sayBye"/>
        </wsdl:message>
        <wsdl:message name="sayByeResponse">
            <wsdl:part name="parameters" element="ns:sayByeResponse"/>
        </wsdl:message>
        <wsdl:portType name="GreetPortType">
            <wsdl:operation name="echoMessage">
                <wsdl:input message="ns:echoMessageRequest" wsaw:Action="urn:echoMessage"/>
                <wsdl:output message="ns:echoMessageResponse" wsaw:Action="urn:echoMessageResponse"/>
            </wsdl:operation>
            <wsdl:operation name="sayHi">
                <wsdl:input message="ns:sayHiRequest" wsaw:Action="urn:sayHi"/>
                <wsdl:output message="ns:sayHiResponse" wsaw:Action="urn:sayHiResponse"/>
            </wsdl:operation>
            <wsdl:operation name="sayBye">
                <wsdl:input message="ns:sayByeRequest" wsaw:Action="urn:sayBye"/>
                <wsdl:output message="ns:sayByeResponse" wsaw:Action="urn:sayByeResponse"/>
            </wsdl:operation>
        </wsdl:portType>
        <wsdl:binding name="GreetSoap11Binding" type="ns:GreetPortType">
            <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
            <wsdl:operation name="echoMessage">
                <soap:operation soapAction="urn:echoMessage" style="document"/>
                <wsdl:input>
                    <soap:body use="literal"/>
                </wsdl:input>
                <wsdl:output>
                    <soap:body use="literal"/>
                </wsdl:output>
            </wsdl:operation>
            <wsdl:operation name="sayHi">
                <soap:operation soapAction="urn:sayHi" style="document"/>
                <wsdl:input>
                    <soap:body use="literal"/>
                </wsdl:input>
                <wsdl:output>
                    <soap:body use="literal"/>
                </wsdl:output>
            </wsdl:operation>
            <wsdl:operation name="sayBye">
                <soap:operation soapAction="urn:sayBye" style="document"/>
                <wsdl:input>
                    <soap:body use="literal"/>
                </wsdl:input>
                <wsdl:output>
                    <soap:body use="literal"/>
                </wsdl:output>
            </wsdl:operation>
        </wsdl:binding>
        <wsdl:binding name="GreetSoap12Binding" type="ns:GreetPortType">
            <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
            <wsdl:operation name="echoMessage">
                <soap12:operation soapAction="urn:echoMessage" style="document"/>
                <wsdl:input>
                    <soap12:body use="literal"/>
                </wsdl:input>
                <wsdl:output>
                    <soap12:body use="literal"/>
                </wsdl:output>
            </wsdl:operation>
            <wsdl:operation name="sayHi">
                <soap12:operation soapAction="urn:sayHi" style="document"/>
                <wsdl:input>
                    <soap12:body use="literal"/>
                </wsdl:input>
                <wsdl:output>
                    <soap12:body use="literal"/>
                </wsdl:output>
            </wsdl:operation>
            <wsdl:operation name="sayBye">
                <soap12:operation soapAction="urn:sayBye" style="document"/>
                <wsdl:input>
                    <soap12:body use="literal"/>
                </wsdl:input>
                <wsdl:output>
                    <soap12:body use="literal"/>
                </wsdl:output>
            </wsdl:operation>
        </wsdl:binding>
        <wsdl:binding name="GreetHttpBinding" type="ns:GreetPortType">
            <http:binding verb="POST"/>
            <wsdl:operation name="echoMessage">
                <http:operation location="Greet/echoMessage"/>
                <wsdl:input>
                    <mime:content type="text/xml" part="echoMessage"/>
                </wsdl:input>
                <wsdl:output>
                    <mime:content type="text/xml" part="echoMessage"/>
                </wsdl:output>
            </wsdl:operation>
            <wsdl:operation name="sayHi">
                <http:operation location="Greet/sayHi"/>
                <wsdl:input>
                    <mime:content type="text/xml" part="sayHi"/>
                </wsdl:input>
                <wsdl:output>
                    <mime:content type="text/xml" part="sayHi"/>
                </wsdl:output>
            </wsdl:operation>
            <wsdl:operation name="sayBye">
                <http:operation location="Greet/sayBye"/>
                <wsdl:input>
                    <mime:content type="text/xml" part="sayBye"/>
                </wsdl:input>
                <wsdl:output>
                    <mime:content type="text/xml" part="sayBye"/>
                </wsdl:output>
            </wsdl:operation>
        </wsdl:binding>
        <wsdl:service name="Greet">
            <wsdl:port name="GreetHttpSoap11Endpoint" binding="ns:GreetSoap11Binding">
                <soap:address location="http://localhost:8080/axis2/services/Greet"/>
            </wsdl:port>
            <wsdl:port name="GreetHttpSoap12Endpoint" binding="ns:GreetSoap12Binding">
                <soap12:address location="http://localhost:8080/axis2/services/Greet"/>
            </wsdl:port>
            <wsdl:port name="GreetHttpEndpoint" binding="ns:GreetHttpBinding">
                <http:address location="http://localhost:8080/axis2/services/Greet"/>
            </wsdl:port>
        </wsdl:service>
    </wsdl:definitions>I have also added the following line in my services.xml,
    <schema schemaNamespace="http://localhost:8080/Fws/services/Greet?xsd" />
    Kindly let me know how to solve this.
    TIA,
    Jade

    Looks like error is clear namespace mismatch...try changing the following url in wsdl and regen the code
    http://example.ws found http://example.ws/xsd

  • Please help with error message invoking external service from BPEL

    Yes, I'm new to Oracle SOA Suite and BPEL Process manager. I've searched the forums, OTN, and Google and have not found any description of this error message:
    "oracle.fabric.common.FabricException: Number of SOAP body elements and parts do not match in operation: <operation-name>"
    Using JDeveloper 11.1.1.2.0 and WebLogic/SOA 10.3.2.0.
    The BPEL process was built completely using JDeveloper's graphical tools... I haven't done any raw editing of the BPEL files yet. What types of things might I possibly be doing wrong that would cause this error to occur? Any idea what two things the server is comparing and deciding that there's a mismatch? It doesn't look like it is even attempting to invoke the external service, but bailing out before that, thinking that it's going to send bad data. Below is a bit more detail.
    Also, I loaded up the WSDL (same one that I gave to JDeveloper) into SOAPUI. Then I took the payload that SOA was about to send (see below) and pasted it into SOAPUI. SOAPUI didn't complain and the target web service accepted the message and produced a "success" response. It looks like the payload is correct, so I don't know why SOA is complaining.
    Thanks for any help you can offer.
    =====================================================
    Faulted while invoking operation "UpsertEmp" on provider "SiebelUSEmployeeIntegration".
    <messages>
    <input>
    <UpsertEmpInput>
    <part name="SiebelMessage">
    <SiebelMessage>
    <ns1:USEmployment>
    <ns1:globalId>123456abcdef</ns1:globalId>
    <ns1:employeeId>000123456</ns1:employeeId>
    <ns1:effDt>1/1/2009</ns1:effDt>
    <ns1:emplStatus>A</ns1:emplStatus>
    <ns1:supported>N</ns1:supported>
    <ns1:employed>Y</ns1:employed>
    <ns1:activeStatus>Y</ns1:activeStatus>
    <ns1:hrEditOnly>Y</ns1:hrEditOnly>
    <ns1:paygroup/>
    <ns1:statusCode/>
    <ns1:origHireDate/>
    <ns1:termDate/>
    <ns1:latestHireDate/>
    <ns1:locationCode/>
    <ns1:locationDescr>Somewhere</ns1:locationDescr>
    <ns1:positionCode/>
    <ns1:jobCode/>
    <ns1:jobDescr/>
    <ns1:supervisorEmplid>000654321</ns1:supervisorEmplid>
    <ns1:deptCode>ITG</ns1:deptCode>
    <ns1:deptDescr>Information Technology Group</ns1:deptDescr>
    <ns1:ministryCode/>
    <ns1:ministryDescr>Core Services</ns1:ministryDescr>
    <ns1:subministryCode/>
    <ns1:subministryDescr>Information Technology Group</ns1:subministryDescr>
    <ns1:wwcFreeSubFlag>N</ns1:wwcFreeSubFlag>
    <ns1:lakeHartMC>1234</ns1:lakeHartMC>
    <ns1:testFlag>Y</ns1:testFlag>
    </ns1:USEmployment>
    </SiebelMessage>
    </part>
    </UpsertEmpInput>
    </input>
    <fault>
    <bpelFault>
    <faultType>
    <message>0</message>
    </faultType>
    <remoteFault>
    <part name="summary">
    <summary>oracle.fabric.common.FabricException: Number of SOAP body elements and parts do not match in operation: UpsertEmp</summary>
    </part>
    <part name="detail">
    <detail>Number of SOAP body elements and parts do not match in operation: UpsertEmp</detail>
    </part>
    </remoteFault>
    </bpelFault>
    </fault>
    <faultType>
    <message>0</message>
    </faultType>
    </messages>

    Welcome to BPEL. Take a moment, and write "it's a namespace issue" on a sheet of paper. Post it near your monitor. It won't always be a namespace issue, but it's usually a good thing to suspect first! Is the namespace prefix ns1: defined somewhere? Does your XML that is being sent really match what the WSDL has for input to the UpsertEmp operation? The namespaces for each element level in the XML need to match, not just the lowest level.
    When problems like this get really sticky, you can use TCP tunneling (obtunnel shell?) to capture what is really being sent to the server, and compare that to what is sent from SOAPUI. That's more useful if it's a subtle header problem, but you may get better error messages if you catch the BPEL message and send it using SOAPUI.
    Good Luck, Andy

  • Error running Ant to Test a BPEL process in developer-prompt

    Hi,
    I am trying to start an Ant-script to start a testsuite for a BPEL process. It fails ...
    Im running the defult Ant script (build.xml) from the Developer-prompt. It works fine from within JDeveloper Studio.
    Anyone who can help me??
    Thx
    Norvald
    Error messages:
    [bpeltest] <Line 39, Column 173>: XML-22016: (Error) Extension function namespace should start with 'http://www.oracle.com/XSL/Transform/java/'.
    and
    C:\product\jdevstudio\jdev\mywork\HelloWorld\HelloWorldProcess\build.xml:197: Could not find a valid processor version implementation from oracle.xml.jaxp.JXSAXTransformerFactory
    The complete output from the Ant build (including errors):
    C:\product\jdevstudio\jdev\mywork\HelloWorld\HelloWorldProcess>ant test
    Buildfile: build.xml
    Trying to override old definition of task customize
    prepareTests:
    [echo]
    [echo] --------------------------------------------------------------
    [echo] | Preparing BPEL tests for deployment
    [echo] --------------------------------------------------------------
    [echo]
    [delete] Deleting: C:\product\jdevstudio\jdev\mywork\HelloWorld\HelloWorldPro
    cess\output\bpeltest.zip
    [zip] Building zip: C:\product\jdevstudio\jdev\mywork\HelloWorld\HelloWorl
    dProcess\output\bpeltest.zip
    deployTestSuites:
    [echo]
    [echo] --------------------------------------------------------------
    [echo] | Deploying bpel tests HelloWorldProcess on localhost, port 8888
    [echo] --------------------------------------------------------------
    [echo]
    [deployTestSuites] Deploying C:\product\jdevstudio\jdev\mywork\HelloWorld\HelloW
    orldProcess\output\bpeltest.zip...
    [deployTestSuites] Accesing URL /integration/services/deploy/integration/service
    s/deploy/deployTests.jsp
    [deployTestSuites] status [200] received from server
    [deployTestSuites] wrapped response
    [deployTestSuites] End of the deployment
    [deployTestSuites] bpeltest.zip deployed successfully.
    bpelTest:
    [echo]
    [echo] --------------------------------------------------------------
    [echo] | Executing process HelloWorldProcess(v.1.0): minCoverage=100%, time
    out=90 sec, numWorkers=1
    [echo] --------------------------------------------------------------
    [echo]
    [delete] Deleting directory C:\product\jdevstudio\jdev\mywork\HelloWorld\Hell
    oWorldProcess\test-results\xml\HelloWorldProcess
    [bpeltest] connecting to /integration/services/deploy/xmlRunTests.jsp
    [bpeltest] <Line 39, Column 173>: XML-22016: (Error) Extension function namespa
    ce should start with 'http://www.oracle.com/XSL/Transform/java/'.
    [echo]
    [echo] --------------------------------------------------------------
    [echo] Executed 2 test(s) for HelloWorldProcess (v.1.0) with 0 failure(s)
    [echo] --------------------------------------------------------------
    [echo]
    report:
    [echo]
    [echo] --------------------------------------------------------------
    [echo] Creating BPELTest JUnitReport at C:\product\jdevstudio\jdev\mywork\H
    elloWorld\HelloWorldProcess/test-results\html\index.html
    [echo] --------------------------------------------------------------
    [echo]
    BUILD FAILED
    C:\product\jdevstudio\jdev\mywork\HelloWorld\HelloWorldProcess\build.xml:197: Co
    uld not find a valid processor version implementation from oracle.xml.jaxp.JXSAX
    TransformerFactory
    Total time: 14 seconds

    sorry for the late reply. The problem is that Oracle XDK is not compatible with the junitreport task. I believe there are some post install steps (due to licensing issues) that you need to perform before running the ant task. This is noted in the release notes (copied below):
    1. base site for xalan is http://xml.apache.org/xalan-j/ site. to download, go to: http://www.apache.org/dyn/closer.cgi/xml/xalan-j. then from the recommended mirror site download xalan-j_2_7_0-bin.zip.
    2. unzip this file.
    3. copy unzip_dir\xalan-j_2_7_0\serializer.jar to Oracle_Home\bpel\lib\serializer_2.7.0.jar. copy unzip_dir\xalan-j_2_7_0\xalan.jar to Oracle_Home\bpel\lib\xalan_2.7.0.jar. Note the filename change
    4. no change to obsetenv is needed.

  • ReferenceError: Error #1065: Variable @namespace is not defined.

    I am using FB4 but SDK 3.5.  I created a webservice to call a webservice by .Net.  The related codes are listed below
    <mx:WebService id="ws"   wsdl="{URL_WSDL2}" fault="wsHandleFault(event)"  useProxy="false"  >
      <mx:operation name="GetDistrict"
       resultFormat="object"
       result="GetDistrict(event)" />
      <mx:operation name="GetStates"
       resultFormat="object"
       result="GetStates(event)" />
    </mx:WebService>
    private function LoadData():void {;
      ws.getOperation("GetDistrict").send();
      ws.getOperation("GetStates").send();
      btnLoad.enabled = false;
    However, I got runtime error:
    ReferenceError: Error #1065: Variable @namespace is not defined.
    at mx.rpc.xml::SchemaLoader/schemaImports()
    at mx.rpc.wsdl::WSDLLoader/schemaImports()
    at mx.rpc.wsdl::WSDLLoader/resultHandler()
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at HTTPOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
    at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler()
    at mx.rpc::Responder/result()
    at mx.rpc::AsyncRequest/acknowledge()
    at DirectHTTPMessageResponder/completeHandler()
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/onComplete()
    I really don't know how to fix it.  Wish someone can share his/her experience.  Thanks.

    When creating a Web Service in .NET, specifically a WCF based Web Service, the auto generated code tends to have an empty namespace (for you to fill). If you specify a namespace for the service contract and behavior this tends to resolve the Flex issue.
    e.g. in your .NET service or service interface code you can specify them as attributes and would look something like:
    ' VB
    Imports System.ServiceModel
    <ServiceContract(Namespace:="http://somedomain.com")>
    <ServiceBehavior(Namespace:="http://somedomain.com")>
    Public Class MyWebService
    // C#
    using System.ServiceModel;
    [ServiceContract(Namespace:="http://somedomain.com")]
    [ServiceBehavior(Namespace:="http://somedomain.com")]
    public class MyWebService
    Hope that helps someone!
    (I realise this post is a bit old, but shows up high in Google for the error message, so have posted for the benefit of anyone finding it)

  • Org.apache.axis2.AxisFault: namespace mismatch require

    hello Friends,
    I am doing an Axis2 WebService, i have done every thing like created .arr, Depoyed , i have generated stub , i wrote client every thing is working fine but when i run my client it is showing the following error.
    org.apache.axis2.AxisFault: namespace mismatch require http://example.ws found http://example.ws/xsddo any one have idea why i am getting this error.
    thanQ for any kind of error.
    Han

    Pls check your wsdl file. If the wsdl file is wrong, then ServiceBuilder takes the default wsdl and it uses the package structure to create default namespace (which is example.ws in ur case). Check your wsdl for proper binding, port and service declarations.

  • Error #13 - XMLExporter Type mismatch

    I have a customer using Access 2003 and SQL Developer 1.5.0.53
    During the migration process with using Qucik migration or generating XML file
    he gets an Type Mismatch from Access
    I have used the older version of SQL Developer which was 1.2 and did not run into this issue. Looks like something has changed or needs to be changed.

    Hi,
    Could you please confirm the version of the Exporter tool you used? From what I can recall, the same version of the Exporter was shipped with 1.5 as was shipped with 1.2, which is 10.2.0.2.5.
    Please refer to the following related thread, where you have also posted your issue - Re: Error #13 - XMLExporter - Type mismatch I would recommend following the Diagnosing Exporter Problems announcement on the Microsoft Access Migration to Oracle APEX forum - http://forums.oracle.com/forums/ann.jspa?annID=376, and ensure that you have carried out the necessary steps on your MDB file.
    Have you tried using another version of the Exporter tool?
    Regards,
    Hilary

  • Error while invoking web service from BPEL 11g

    Hello All,
    I am creating a webservice using java.
    I created service using java and deployed it on the SOA server 11g.
    I am able to test it from the weblogic console.
    When i am trying to invoke it from BPEL, i am getting the remote fault:
    Error Message: {http://schemas.oracle.com/bpel/extension}remoteFault
    Fault ID default/TestADWebServiceBPEL!1.0soa_d7638bee-192e-419e-9b1a-2f356c13712c/TestADServiceBPEL/80015-BpInv0-BpSeq0.3-3*
    Fault Time Sep 28, 2010 1:31:01 PM
    Non Recoverable System Fault :
    <bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://10.6.61.93:7001/TestApplication-ADUserManagement-context-root/ActiveDirectoryUserPort</summary></part><part name="detail"><detail>Unable to access the following endpoint(s): http://10.6.61.93:7001/TestApplication-ADUserManagement-context-root/ActiveDirectoryUserPort</detail></part><part name="code"><code>200</code></part></remoteFault></bpelFault>
    Does anyone has any idea, what can be the reason.
    Is it realted to some proxy server settings. Where these settings can be made in the weblogic server.
    Thanks and Regards,
    Saurav Singla

    Hi Suresh & Mukesh,
    Suresh:
    I started the service by going through the following path System Administrator > System Configuration > Service Configuration > Application > <SERVICE_NAME> in system configuration of portal
    Mukesh: Here I don't have any proxy settings.
    Can you please let me know where I'm going wrong.
    Thanx,
    Dheeram

  • Error while checking the flow of bpel process in bpel console

    Hi Experts
    I have created one bpel process which invokes task manager for approving or rejecting the leave request. I ve successfully deployed the bpel process and also able to test approve or reject the leave request . But i am facing one error
    when i am initiate a bpel process and started to check the flow of that bpel process in bpelconsole it gives me some error message in small pop up like
    error : Internal/ bug ( #589 )
    \u017E is not defined
    i click Ok and after this no error and all working well.
    Thanks.

    A quick answer is:
    1. make sure you defined the Application/Integration Server in your developer (user/pass you have - if not oc4jadmin then one the IT gave you).
    2. Deploy your project to that server.
    3. Choose the correct domain in the Console when deploying.
    Is this what you wanted to know???

  • How to fix an error  (related to work schedule rule) in Time evaluation ?

    Hi experts,
    I am getting an error while running time evaluation - PT60.
    Find the log
    Log:TimeEvaluation                                                                                General data                                                                       
    Schema ZM04 Time Evaluation Without Clock Times
    00753402 Christoudas Natalie
    Customizing error in work schedule rule 1 VM 01 5MTWTF Person rejected: 00753402
    How to fix it? Its urgent.
    Be assured of points for useful answers.
    Rajesh

    Hi All,
    I have checked work schedules and work sc. rules. everything looks fine. Reason being fine, same work schrdule rule, i.e. 5MTWTF is used for other employees, whose payroll area, personnel area, personnel subarea, employee group and employee subgroups are same.
    Why it is throwing error for one employee 753402.
    I am providing you more information. In table V_T569r, if u select recalculation category as time evaluation, it is mentioned as 01.01.2003. Initially, one action called "Conversion take on" has been maintained as on 01.03.2002, where employee had payroll area -99 (payroll irrelevant) and personnel subarea - DAYY.
    Then on 17.03.2008, another action ran "Conversion initial reassignment" where payroll area changed to "MT - monthly", subarea changed to DAYF. At that time PDC recalculation date in infotype 0003 was 01.03.2002 which was before recalculation date, i.e. 01.01.2003.
    Time evaluation was throwing 2 error messages. one was solved by changing PDC recaluation date to 17.03.2008. But other error related to work sc rule 1 VM 01 5MTWTF still occurs. 
    Can some body now provide some useful information?
    Thanks
    Rajesh

  • Error while using DB Adapter in BPEL process

    Hi All,
    I am getting error while using DB Adapter in BPEL process
    java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DevDBAdapter' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. DBAdapterDemo:DevDBAdapter [ DevDBAdapter_ptt::DevDBAdapter(InputParameters,OutputParameters) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/Dev'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/Dev. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) 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:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:157) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1259) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:698) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:285) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DevDBAdapter' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. DBAdapterDemo:DevDBAdapter [ DevDBAdapter_ptt::DevDBAdapter(InputParameters,OutputParameters) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/Dev'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/Dev. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:985) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 69 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DevDBAdapter' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. DBAdapterDemo:DevDBAdapter [ DevDBAdapter_ptt::DevDBAdapter(InputParameters,OutputParameters) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/Dev'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/Dev. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:955) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:750) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:234) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:105) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 72 more
    I have created jndi from console which I have mentioned in DBAdapter and I have provided details of JNDI to DbAdapter in deployment.
    I am not able to solve this.
    Can you please let me know solution for this or provide me link for tutorial of DBAdapter for stored procdure call?

    did u deploy your dbadapter through console to the plan mentioned for deployment?

  • Error updating a Human Task in BPEL

    Hi,
    I have a requirement where in i need bpeladmin to update a task assigned to some group.
    While doing so ,as task is assigned to group i first acquire the task and then perform update on the task
    While performing updation i am getting following
    Invalid action on workflow task.
    Action UPDATE on task a7a61c38dd54a6cb:d9506a8:121a07d45ee:-7aa7 is not valid because of .
    Contact oracle support if error is not fixable.
    at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3416)
    at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3440)
    at oracle.bpel.services.workflow.task.impl.TaskService.addComment(TaskService.java:617)
    at oracle.bpel.services.workflow.task.impl.TaskService.addComment(TaskService.java:639)
    at oracle.bpel.services.workflow.task.ejb.TaskServiceBean.addComment(TaskServiceBean.java:167)
    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 java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:396)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:622)
    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.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
    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 TaskServiceBean_RemoteProxy_68d4144.addComment(Unknown Source)
    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.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: ORABPEL-30036
    Invalid action on workflow task.
    Action UPDATE on task a7a61c38dd54a6cb:d9506a8:121a07d45ee:-7aa7 is not valid because of The task has been acquired by some other user..
    Contact oracle support if error is not fixable.
    at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3408)
    ... 32 more
    exception is ORABPEL-30036
    Invalid action on workflow task.
    Action UPDATE on task a7a61c38dd54a6cb:d9506a8:121a07d45ee:-7aa7 is not valid because of .
    Contact oracle support if error is not fixable.
    When i check wftask table in database , acquiredby column it shows entry as bpeladmin
    Following is the code snippet that i am using to perform the task
    Task objTask=wfSvcClient.getTaskService().acquireTask(wfCtx,"a7a61c38dd54a6cb:d9506a8:121a07d45ee:-7aa7");
         objTask=wfSvcClient.getTaskService().addComment(wfCtx, "a7a61c38dd54a6cb:d9506a8:121a07d45ee:-7aa7", "abc123");
         List assigneeGroupLst=objTask.getSystemAttributes().getAssigneeGroups();
         String assigneeGroup=null;
         if(null!=assigneeGroupLst && assigneeGroupLst.size()>0){
              assigneeGroup=((IdentityType)assigneeGroupLst.get(0)).getId();
         SystemMessageAttributesType sysAttr=objTask.getSystemMessageAttributes();
         sysAttr.setProtectedTextAttribute1(assigneeGroup);
         wfSvcClient.getTaskService().updateTask(wfCtx, objTask);
    The context created is for user BPELAdmin user.
    Do i need to give any rights to bpeladmin? Or is there some other way of doing it.
    Any help appreciated !!!
    Regards,
    Bhavik

    Hi Anirudh,
    Thanks for quick reply.
    I have a requirement where based on certain condition i need to update the task and reassign it.
    There is a batch that runs and performs the task. While doing so i dont have any info as to whom
    the task is assigned.
    So i am using bpeladmin to perform the task.
    If task is assigned to user and i try to update the task using bpeladmin then am able to do so.
    But if the task is assigned to Group i am getting the error. If task is assigned to user, i am able to
    acquire the task but not able to update the task.
    While updation it shows the task has been acquired by some other user.
    Is there any other way by which i can implement the same ?
    Regards,
    Bhavik

  • Errors in direct binding invocation from BPEL to OSB

    Hi All,
    I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
    There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
    Any help about the management of this situation would be appreciated.
    Thanks,
    The log trace is the next one:
    [component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
         at java.lang.Thread.run(Thread.java:662)
    And this is the payload from the instance details:
    <messages>
    <input>
    ... input data....
    </input>
    <fault>
    <exception class="com.collaxa.cube.engine.EngineException">
    JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
    <stack>
    <f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
    <f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
    <f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
    <f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
    <f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
    <f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
    <f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
    <f>...</f>
    </stack>
    </exception>
    <root class="oracle.fabric.common.FabricInvocationException">
    oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
    <stack>
    <f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
    <f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
    <f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
    <f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
    <f>java.security.AccessController.doPrivileged</f>
    <f>javax.security.auth.Subject.doAs#396</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
    <f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
    <f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
    <f>java.lang.reflect.Method.invoke#597</f>
    <f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
    <f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
    <f>...</f>
    </stack>
    </root>
    </fault>
    </messages>
    Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

    Hi All,
    I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
    There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
    Any help about the management of this situation would be appreciated.
    Thanks,
    The log trace is the next one:
    [component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
         at java.lang.Thread.run(Thread.java:662)
    And this is the payload from the instance details:
    <messages>
    <input>
    ... input data....
    </input>
    <fault>
    <exception class="com.collaxa.cube.engine.EngineException">
    JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
    <stack>
    <f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
    <f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
    <f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
    <f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
    <f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
    <f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
    <f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
    <f>...</f>
    </stack>
    </exception>
    <root class="oracle.fabric.common.FabricInvocationException">
    oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
    <stack>
    <f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
    <f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
    <f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
    <f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
    <f>java.security.AccessController.doPrivileged</f>
    <f>javax.security.auth.Subject.doAs#396</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
    <f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
    <f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
    <f>java.lang.reflect.Method.invoke#597</f>
    <f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
    <f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
    <f>...</f>
    </stack>
    </root>
    </fault>
    </messages>
    Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

  • Error #1063: Argument count mismatch on CBClasses::cbIntro(). Expected 5, got 0

    Hi,
    This is my first attempt with AS3...now I am well aware of OOPs concepts and am comfortable with programming, but I am not able to wrap my head around the whole connecting the classes to the display objects on screen thing [linkages and class names n all]..now I managed to fix most errors in my file, which has cbIntro as the base class [set up successfully]...now cbIntro extends MovieClip as it links to an external fla [cbFlash]...but  within cbFLash I am calling the following...
    import CBClasses.cbIntro;
    var flipped:Boolean = false;
    var jobs:jobsBtn_mc = new jobsBtn_mc();  //not a button a movieclip within the library
    var flip:cbIntro;
    function callFlip(e:MouseEvent):void 
    trace("in call flip");
    if (!flipped)
    //some button code
    flip  = new cbIntro(evnts, jobs, 2, "left", true);  //evnts is a mc on stage
    addChild(flip);
    flipped = true;  
    else if (flipped)
    flip = new cbIntro(jobs, evnts, 2, "right", true); 
    addChild(flip); 
    flipped = false; 
    evnts.nxt.visible = true; 
    evnts.nxt.addEventListener(MouseEvent.MOUSE_DOWN, callFlip); //Adds the listeners to the buttons 
    jobs.bck.addEventListener(MouseEvent.MOUSE_DOWN, callFlip); 
    cbIntro has one constructor which takes 5 parameters, defined within a separate .as file.....now I am getting an error
    Error #1063: Argument count mismatch on CBClasses::cbIntro(). Expected 5, got 0 
    How can this happen, the only time an object is created, I am sending the right number of parameters...?? declaring a cbIntro variable should not call the constructor....?? Is that what is happening?? Or am I missing something important????

    Hi Ned,
    Sorry about posting two different topics thing...I was just trying to figure out the first problem by creating a stripped down version of the sending an on stage movieclip to an external class thing. I don't know how I can break up this post now...but since you have mentioned a few points...the problem is not with the private function declaration..you are correct of course..and that error was fixed..but I am still getting the error....
    inside intromain constructor
    Error: Error #2136: The SWF file file:///E|/Adobe/Flash%20CS5/Projects/trial/introduction.swf contains invalid data.
    at introMain/frame1()
    the introMain class only contains a constructor and a vanish function, which only shows a trace. I removed the problem with the on stage instance name, and tried to access it directly...but I don't think the code is even getting to that point...or may be it is...I am at a loss here...
    Code within introduction.swf
    var iMain:introMain = new introMain();
    var isVanished:Boolean = false;
    trace("events alpha" + eventsmc.alpha);
    I am not even calling the vanish function anymore...is something wrong with the constructor call???
    Code within introMain
    package  {
    import flash.display.*;
    import fl.transitions.easing.*;
    import fl.transitions.Tween;
    import fl.transitions.TweenEvent;
    import flash.events.MouseEvent;
    public class introMain extends MovieClip{
              public function introMain(){
                   trace("inside intromain constructor");
               public function vanish(mcName:MovieClip):void{
                 trace("inside vanish");

  • ArgumentError: Error #1063: Argument count mismatch on portfolio_fla::MainTimeline/loadFightBite().

    Hi
    I'm trying to load a swf onto my stage and I'm having some problems with the event handler. I'm getting an error: when I comment out the event handler, it returns no errors, I've tried the function both with and without void, but it doesn't fix the error. I know this should be an easy fix, but it's got me stumped. Can anybody help? Thanks guys.
    ArgumentError: Error #1063: Argument count mismatch on portfolio_fla::MainTimeline/loadFightBite(). Expected 0, got 1.
    var fightBite_mc:MovieClip;
    var swfLoader:Loader = new Loader ();
    var swfRequest:URLRequest;
    fightBite_but.addEventListener (MouseEvent.CLICK, loadFightBite);
    function loadFightBite():void {
         this.addChild(swfLoader);
         swfLoader.load(new URLRequest("ftb_preloader.swf"));
         swfLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, swfLoaded);
    function swfLoaded(loadEvent:Event){
         swfLoader.x = stage.stageHeight /2;
         swfLoader.y = stage.stageWidth /2;
         swfLoader.contentLoaderInfo.removeEventListener(Event.COMPLETE, swfLoaded);
         fightBite_mc=swfLoader.content as MovieClip;

    use:
    var fightBite_mc:MovieClip;
    var swfLoader:Loader = new Loader ();
    var swfRequest:URLRequest;
    fightBite_but.addEventListener (MouseEvent.CLICK, loadFightBite);
    function loadFightBite(e:MouseEvent):void {
         this.addChild(swfLoader);
         swfLoader.load(new URLRequest("ftb_preloader.swf"));
         swfLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, swfLoaded);
    function swfLoaded(loadEvent:Event:Event){
         swfLoader.x = stage.stageHeight /2;
         swfLoader.y = stage.stageWidth /2;
         swfLoader.contentLoaderInfo.removeEventListener(Event.COMPLETE, swfLoaded);
         fightBite_mc=swfLoader.content as MovieClip;

Maybe you are looking for

  • Problem in Transporting the changes in Payslip  after inclusion of new WT

    Dear Experts, Here we have added the new wagetypes in Payslip Through Transction code  PE51  in Dev Client.And the changes were saved in a Transport request.After movement to Quality the respective changes are not shown up.Then we checked the  Transp

  • IPad 2 with dock and smart cover?

    Can you put the iPad2 in the charging dock with the smart cover on? thanks, tom

  • Forms 9i: Documentation, Samples

    Are there any documentation or samples on how to use the JDAPI and XMLTOOLS packages for Forms 9i that can be downloaded? Draft versions of books would be very nice (or are there published books already?) Thanks.

  • Info disappeared when I rebooted my computer!

    I have just rebooted my computer and reinstalled all the programs I need, including iTunes. Of course I saved all of my music and my iTunes library file before I rebooted. Almost all the info I added about the music in my library is still there, but

  • Essbase data load in the background...can't find error file

    I just loaded a big text file (90GB) to an ASO cube. I clicked on Run in the background option. The process was over after 3-4 hours. I can see the number of input cells and nothing in active session. But I don't see an error file created...I'm sure