Urgent : Fault Policies(MDS) in 11g

Hi All,
i am trying to use fault policies in 11g. In my project i've only one composite with 2 BPEL.
As per documentation i can have
1). the fault policies and fault bindings in the same composite. this is working fine.
2). In a different location that is specified with two properties that you add to the composite.xml file.the fault policy files are placed into the SOA Metadata Service (MDS) shared area.
In the second Scenario, where do i need to place my fault-policies.xml and fault-bindings.xml in Server(MDS). Do i need to create any Repository in my Enterprise Manager Console. What would be the Architecture of this. Any working example and pointer to setup the properties files will be great help.
Currently My fault-policies.xml and fault-bindings.xml are in my local JDeveloper home. And i've JDeveloper in my desktop accessing Remote Server.
Composite.xml
=======================
<?xml version="1.0" encoding="UTF-8" ?>
<!-- Generated by Oracle SOA Modeler version 1.0 at [6/3/10 5:17 PM]. -->
<composite name="FMF_Demo"
revision="3.0"
label="2010-06-03_17-17-58_121"
mode="active"
state="on"
xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
xmlns:ui="http://xmlns.oracle.com/soa/designer/">
<import namespace="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FaultHandlerDemo"
location="FaultHandlerDemo.wsdl" importType="wsdl"/>
<import namespace="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FMF_CallingProcess"
location="FMF_CallingProcess.wsdl" importType="wsdl"/>
<service name="faulthandlerdemo_client_ep"
ui:wsdlLocation="FaultHandlerDemo.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FaultHandlerDemo#wsdl.interface(FaultHandlerDemo)"/>
<binding.ws port="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FaultHandlerDemo#wsdl.endpoint(faulthandlerdemo_client_ep/FaultHandlerDemo_pt)"/>
</service>
<service name="fmf_callingprocess_client_ep"
ui:wsdlLocation="FMF_CallingProcess.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FMF_CallingProcess#wsdl.interface(FMF_CallingProcess)"
callbackInterface="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FMF_CallingProcess#wsdl.interface(FMF_CallingProcessCallback)"/>
<binding.ws port="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FMF_CallingProcess#wsdl.endpoint(fmf_callingprocess_client_ep/FMF_CallingProcess_pt)"/>
<callback>
<binding.ws port="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FMF_CallingProcess#wsdl.endpoint(fmf_callingprocess_client_ep/FMF_CallingProcessCallback_pt)"/>
</callback>
</service>
<property name="oracle.composite.faultPolicyFile">oramds:/apps/faultpolicyfiles/fault-policies.xml</property>
<property name="oracle.composite.faultBindingFile">oramds:/apps/faultpolicyfiles/fault-bindings.xml</property>
<component name="FaultHandlerDemo">
<implementation.bpel src="FaultHandlerDemo.bpel"/>
</component>
<component name="FMF_CallingProcess">
<implementation.bpel src="FMF_CallingProcess.bpel"/>
</component>
<wire>
<source.uri>faulthandlerdemo_client_ep</source.uri>
<target.uri>FaultHandlerDemo/faulthandlerdemo_client</target.uri>
</wire>
<wire>
<source.uri>fmf_callingprocess_client_ep</source.uri>
<target.uri>FMF_CallingProcess/fmf_callingprocess_client</target.uri>
</wire>
<wire>
<source.uri>FMF_CallingProcess/FaultHandlerDemo.faulthandlerdemo_client</source.uri>
<target.uri>FaultHandlerDemo/faulthandlerdemo_client</target.uri>
</wire>
</composite>
fault-bindings.xml
========================================
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicyBindings version="0.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<composite faultPolicy="FusionMidFaults"/>
<!--<composite faultPolicy="ServiceExceptionFaults"/>-->
<!--<composite faultPolicy="GenericSystemFaults"/>-->
</faultPolicyBindings>
fault-policies.xml
========================================
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<faultPolicy version="0.0.1" id="FusionMidFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:flt="http://xmlns.oracle.com/Application1_jws/FMF_Demo/FaultHandlerDemo" name="flt:BusinessFaultMessage_1">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
<condition>
<action ref="ora-java"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
<condition>
<action ref="ora-java"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:runtimeFault">
<condition>
<action ref="ora-java"/>
</condition>
</faultName>
</Conditions>
<Actions>
<!-- Generics -->
<Action id="ora-retry">
     <retry>
<retryCount>3</retryCount>
<retryInterval>2</retryInterval>
<exponentialBackoff/>
</retry>
</Action>
<Action id="ora-terminate">
<abort/>
</Action>
<Action id="ora-replay-scope">
<replayScope/>
</Action>
<Action id="ora-rethrow-fault">
<rethrowFault/>
</Action>
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
<Action id="MediatorJavaAction">
<!-- this is user provided class-->
<javaAction className="MediatorJavaAction.myClass" defaultAction="ora-terminate">
<returnValue value="MANUAL" ref="ora-human-intervention"/>
</javaAction>
</Action>
<Action id="ora-java">
<!-- this is user provided class-->
<javaAction className="BPELJavaAction.myAnotherClass" defaultAction="ora-human-intervention">
<returnValue value="MANUAL" ref="ora-human-intervention"/>
</javaAction>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
Thanks
Rahul.

Hi,
I created a MAR deployment profile and tried to place the fault-policies.xml and fault-bindings.xml in MDS. I think I am approaching in the wrong way can anyone tell me the right way to place the files in MDS.
Also if I want to use ora-java where to place the .class file. In 10g we will place it under Oracle_Home/bpel/system/classes .
Anticipate earliest reply
Regards,
Sundar

Similar Messages

  • Urgent : Fault Policies in 11g

    Hi All,
    im trying to use fault policies in 11g. as per documentation i can have
    1). the fault policies and fault bindings in the same composite. this works fine
    2). In a different location that is specified with two properties that you add to the composite.xml file. This option is useful if a fault policy must be used by multiple SOA composite applications. This option overrides any fault policy files that are included in the same directory as the composite.xml file. Example 12-3 provides details about these two properties. In this example, the fault policy files are placed into the SOA Metadata Service (MDS) shared area.
    <property
    name="oracle.composite.faultPolicyFile">oramds://apps/faultpolicyfiles/
    fault-policies.xml
    </property>
    <property
    name="oracle.composite.faultBindingFile">oramds://apps/faultpolicyfiles/
    fault-bindings.xml
    </property>
    Problem Description
    i tried to work on both approches
    Scenario 1
    =====================================================
    1). I have 2 Composites with BPEL process
    2). First composite will have fault policies and binidings in the same project as composite.xml and invokes the second composite
    3). Turn Off the First composite.
    remote fault is propagated and waits for recovery.
    Scenario 1
    =====================================================
    1). I have 2 Composites with BPEL process
    2). First composite will have fault policies and binidings are deployed to shared metadata and invokes the second composite and reffered as shown below
    3). Turn Off the First composite.
    remote fault is not getting propagated and process is getting faulted.
    please find the attached composite.xml file i have used.
    is this the correct way to include the fault policies .. if any body has already worked on fault policies in 11G and accessed them thru share metadata are please suggest me how to resolve this, if not any working example and pointer to setup the properties will be of great help.
    <?xml version="1.0" encoding="UTF-8" ?>
    <!-- Generated by Oracle SOA Modeler version 1.0 at [12/07/09 12:32]. -->
    <composite name="TestHello"
    revision="1.0"
    label="2009-07-12_12-32-01_093"
    mode="active"
    state="on"
    xmlns="http://xmlns.oracle.com/sca/1.0"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
    xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
    xmlns:ui="http://xmlns.oracle.com/soa/designer/">
    <import namespace="http://xmlns.oracle.com/SOAMetaData/TestHello/Lakshmi"
    location="Lakshmi.wsdl" importType="wsdl"/>
    <import namespace="http://xmlns.oracle.com/SOAMetaData/Hello/laks1"
    location="http://INT01723:8001/soa-infra/services/default/Hello/laks1.wsdl"
    importType="wsdl"/>
    <service name="lakshmi_client_ep" ui:wsdlLocation="Lakshmi.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/SOAMetaData/TestHello/Lakshmi#wsdl.interface(Lakshmi)"
    callbackInterface="http://xmlns.oracle.com/SOAMetaData/TestHello/Lakshmi#wsdl.interface(LakshmiCallback)"/>
    <binding.ws port="http://xmlns.oracle.com/SOAMetaData/TestHello/Lakshmi#wsdl.endpoint(lakshmi_client_ep/Lakshmi_pt)"/>
    <callback>
    <binding.ws port="http://xmlns.oracle.com/SOAMetaData/TestHello/Lakshmi#wsdl.endpoint(lakshmi_client_ep/LakshmiCallback_pt)"/>
    </callback>
    <property name="oracle.composite.faultPolicyFile">oramds://apps/faultpolicyfiles/fault-policies.xml</property>
    <property name="oracle.composite.faultBindingFile">oramds://apps/faultpolicyfiles/fault-bindings.xml</property>
    </service>
    <component name="Lakshmi">
    <implementation.bpel src="Lakshmi.bpel"/>
    <property name="oracle.composite.faultPolicyFile">oramds://apps/faultpolicyfiles/fault-policies.xml</property>
    <property name="oracle.composite.faultBindingFile">oramds://apps/faultpolicyfiles/fault-bindings.xml</property>
    </component>
    <reference name="Service1"
    ui:wsdlLocation="http://INT01723:8001/soa-infra/services/default/Hello/laks1.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/SOAMetaData/Hello/laks1#wsdl.interface(laks1)"
    callbackInterface="http://xmlns.oracle.com/SOAMetaData/Hello/laks1#wsdl.interface(laks1Callback)"/>
    <binding.ws port="http://xmlns.oracle.com/SOAMetaData/Hello/laks1#wsdl.endpoint(laks1_client_ep/laks1_pt)"
    location="http://INT01723:8001/soa-infra/services/default/Hello/laks1_client_ep?WSDL"/>
    <callback>
    <binding.ws port="http://xmlns.oracle.com/SOAMetaData/Hello/laks1#wsdl.endpoint(laks1_client_ep/laks1Callback_pt)"/>
    </callback>
    <property name="oracle.composite.faultPolicyFile">oramds://apps/faultpolicyfiles/fault-policies.xml</property>
    <property name="oracle.composite.faultBindingFile">oramds://apps/faultpolicyfiles/fault-bindings.xml</property>
    </reference>
    <wire>
    <source.uri>lakshmi_client_ep</source.uri>
    <target.uri>Lakshmi/lakshmi_client</target.uri>
    </wire>
    <wire>
    <source.uri>Lakshmi/Service1</source.uri>
    <target.uri>Service1</target.uri>
    </wire>
    </composite>
    Thanks
    Nadh
    when i try the second scenario it is not picking up the fault

    A Sample composite.xml for the External fault-policy and fault-binding files.
    <?xml version="1.0" encoding="UTF-8" ?>
    <!-- Generated by Oracle SOA Modeler version 1.0 at [6/3/09 4:09 PM]. -->
    <composite name="Shared_MDS_Fault_Policy_Test"
    revision="1.0"
    label="2009-06-03_16-09-26_218"
    mode="active"
    state="on"
    xmlns="http://xmlns.oracle.com/sca/1.0"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
    xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
    xmlns:ui="http://xmlns.oracle.com/soa/designer/">
    <import namespace="http://xmlns.oracle.com/Shared_MDS_Fault_Policy_App/Shared_MDS_Fault_Policy_Test/Med_SharedMDS_Fault_Policy"
    location="Med_SharedMDS_Fault_Policy.wsdl" importType="wsdl"/>
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/file/Shared_MDS_Fault_Policy_App/Shared_MDS_Fault_Policy_Test/OutFile%2F"
    location="OutFile.wsdl" importType="wsdl"/>
    <service name="Med_SharedMDS_Fault_Policy_ep"
    ui:wsdlLocation="Med_SharedMDS_Fault_Policy.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/Shared_MDS_Fault_Policy_App/Shared_MDS_Fault_Policy_Test/Med_SharedMDS_Fault_Policy#wsdl.interface(execute_ptt)"/>
    <binding.ws port="http://xmlns.oracle.com/Shared_MDS_Fault_Policy_App/Shared_MDS_Fault_Policy_Test/Med_SharedMDS_Fault_Policy#wsdl.endpoint(Med_SharedMDS_Fault_Policy_ep/execute_pt)"/>
    </service>
    *<property name="oracle.composite.faultPolicyFile">oramds:/apps/fault-policies.xml*
    *</property>*
    *<property name="oracle.composite.faultBindingFile">oramds:/apps/fault-bindings.xml*
    *</property>*
    <component name="Med_SharedMDS_Fault_Policy">
    <implementation.mediator src="Med_SharedMDS_Fault_Policy.mplan"/>
    </component>
    <reference name="OutFile" ui:wsdlLocation="OutFile.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/file/Shared_MDS_Fault_Policy_App/Shared_MDS_Fault_Policy_Test/OutFile%2F#wsdl.interface(Write_ptt)"/>
    <binding.jca config="OutFile_file.jca"/>
    </reference>
    <wire>
    <source.uri>Med_SharedMDS_Fault_Policy_ep</source.uri>
    <target.uri>Med_SharedMDS_Fault_Policy/Med_SharedMDS_Fault_Policy</target.uri>
    </wire>
    <wire>
    <source.uri>Med_SharedMDS_Fault_Policy/OutFile</source.uri>
    <target.uri>OutFile</target.uri>
    </wire>
    </composite>
    And also Please make sure that you are refering to correct oramds: location as mentioned by suhariha

  • Fault Policies in soa 11g with email notification

    SOA 11.1.1.3
    I want to implement faulpolicies.xml and send email notification. (for binding ,remote fault after certain retries).Can I use email activity in BPEL catch block for this , what should I add ,in my faultpolicies.xml to trigger email activity
    <?xml version="1.0" encoding="UTF-8"?>
    <faultPolicy version="2.0.1" id="FaultPolicyName"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.oracle.com/bpel/faultpolicy"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Conditions>
    <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    name="bpelx:bindingFault">
    <condition>
    <action ref="ora-retry"/>
    </condition>
    </faultName>
    <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    name="bpelx:runtimeFault">
    <condition>
    <action ref="ora-retry"/>
    </condition>
    </faultName>
    </Conditions>
    <Actions>
    <Action id="ora-retry">
    <retry>
    <retryCount>8</retryCount>
    <retryInterval>2</retryInterval>
    <exponentialBackoff/>
    <retryFailureAction ref="send-notification"/>
    </retry>
    </Action>
    </Actions>
    Also, can anyone please tell which is a better option - using email activity or custom java code in fault
    policies.xml.
    Thanks

    Like Oraacler suggested, you can definitely rethrow the fault to BPEL to send the notification. However, your BPEL fault handlers will become pretty tedious when you have to check for error types in your catch block to retrieve the message and type the e-mail. On top of that, if you have multiple catch blocks in a single process or multiple processes spec'd to throw similar notifications, you will have to add a lot of redundant code. You can definitely externalize the notification to a different process that handles all e-mails, but even that does not take out having multiple invokes on the faulted process.
    Having a fault handler Java class to handle global faults allows you to externalize and standardize exception management and also dramatically minimizes BPEL code. In your Java class you also get the API's to access a lot more information then you will in BPEL allowing you to provide detailed messages. This has been my choice to account for any error that should not happen on a regular basis (binding and remote).
    The only drawback of the Java class is the development piece which can take forever since you have to restart the server after every little change. There is however a way to write a client java class for development on JDeveloper which directly connects to the weblogic-soa dehydration store to look up an instance with a fault and retrieve the fault message. You can then use that message to do your testing/development before finalizing it and moving it to the server.
    Depends on what you decide, let us know if you run into any more constraints and we can definitely try to help you.
    Thanks and good luck!

  • Fault Policies SOA 11g

    Hi All,
    Presently my Fault Policies file looks like
    <?xml version='1.0' encoding='UTF-8'?>
    <faultPolicies>
    <faultPolicy version="2.0.1" id="RejectedMessages">
    <Conditions>
    <faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:getSummaryCSVRecords">
    <condition>
    <action ref="ora-writeToFile"/>
    </condition>
    </faultName>
    <faultName>
    <condition>
    <action ref="ora-rethrow-fault"/>
    </condition>
    </faultName>
    </Conditions>
    <Actions>
    <Action id="ora-writeToFile">
    <fileAction>
    <location>/tmp/Rej_Msgs</location>
    <fileName>PSDRejectedMsg.xml</fileName>
    </fileAction>
    </Action>
    <Action id="ora-rethrow-fault">
    <rethrowFault/>
    </Action>
    </Actions>
    </faultPolicy>
    </faultPolicies>
    So , the rejected messages that are given gets placed onto a file system.
    My Query is , if instead of this i want the rejected message to pass onto a queue that is already present in my SOA 11g instance , what might the configurations i might need.
    Presently , my thoughts are to rename ora-writeToFile to ora-writeToQueue .
    change <fileAction> to <QueueAction> and then providing <location> as deployment profile where Queue is present and <QueueName> as the Queue to be used ,
    will this work???????

    yes...this would work

  • Business faults defined in fault policies for synchonous processing

    Hi everyone,
    I have an issue I would like to use your knowledge. I am re-throwing business faults from a synchronous process to a calling synchronous client. Instead of the business fault a remote fault is being propagated back to the calling client using SOA suite 11g for synchronous SCA components. This then causes the fault policies to trigger an incorrect policy.
    Please see below what happens and the error returned.
    1. I have created a synchronous process called SynchrnousBusinessFault that invokes another synchronous process called SynchrnousThrowBusinessFault.
    2. The SynchrnousThrowBusinessFault re-throws a business fault when receiving a text 'businessfault'.
    3. The fault is automatically propaged back to the calling client SynchrnousBusinessFault without the use of any CatchAll branch. The error re-thrown is correct see below:
    <bpelFault>
    <faultType>
    <message>1</message>
    </faultType>
    <BusinessFault>
    <part name="payload">
    <BusinessFault>
    <FaultCode>1000</FaultCode>
    <FaultMessage>Own Business Fault</FaultMessage>
    </BusinessFault>
    </part>
    </BusinessFault>
    </bpelFault>
    4. The callback client SynchrnousBusinessFault receives the fault and should trigger the fault policies for the business fault I have created. The business fault in the fault policies look as follow:
    <faultName xmlns:ns1="http://www.businessfault/example"
    name="ns1:BusinessFault">
    <condition>
    <action ref="business-fault-handler"/>
    </condition>
    </faultName>
    <Action id="business-fault-handler">
    <humanIntervention/>
    </Action>
    This business fault is not triggered in the fault policies and instead the remote fault policy. The reason is that after the re-thrown of the fault the business fault is followed by another fault. I don't understand where this remote fault comes from or whatever this is expected behaviour. Please see the fault below.
    I can provide the example SCA component if required.
    Many Thanks for your time.
    Ren
    om.oracle.bpel.client.BPELFault: faultName: {{http://www.businessfault/example}BusinessFault} messageType: {{http://xmlns.oracle.com/Synchrnous_scenario_jws/SynchrnousThrowBusinessFault/SynchrnousThrowBusinessFault}FaultMessage} parts: {{ payload=<BusinessFault xmlns="http://www.businessfault/example">  <FaultCode>1000</FaultCode>  <FaultMessage>Own Business Fault</FaultMessage> </BusinessFault> } at com.collaxa.cube.engine.ext.bpel.common.BPELWMPHelper.createBPELFault(BPELWMPHelper.java:1071) at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELThrowWMP.__executeStatements(BPELThrowWMP.java:43) at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:157) at com.collaxa.cube.engine.CubeEngine._performActivity(CubeEngine.java:2585) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2444) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1121) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:322) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4497) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4428) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:685) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:116) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:153) at com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean.syncCreateAndInvoke(BPELEngineBean.java:107) 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.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105) at sun.reflect.GeneratedMethodAccessor756.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55) at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy175.syncCreateAndInvoke(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean_51369e_ICubeEngineLocalBeanImpl.syncCreateAndInvoke(BPELEngineBean_51369e_ICubeEngineLocalBeanImpl.java:911) at com.collaxa.cube.engine.delivery.DeliveryHandler.callCreateAndInvoke(DeliveryHandler.java:784) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:524) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:485) at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:164) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.request(CubeDeliveryBean.java:607) 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.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105) at sun.reflect.GeneratedMethodAccessor756.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55) at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy172.request(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.request(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:829) at oracle.fabric.CubeServiceEngine.request(CubeServiceEngine.java:354) at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139) at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:179) at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:144) 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 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:59) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy185.request(Unknown Source) at oracle.integration.platform.blocks.local.LocalInvocationProcessor.request(LocalInvocationProcessor.java:232) at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.request(WebServiceExternalBindingComponent.java:514) at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139) at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:179) at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:144) 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 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy185.request(Unknown Source) at oracle.fabric.CubeServiceEngine.requestToMesh(CubeServiceEngine.java:784) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:256) at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1009) at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:512) at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:123) at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:63) at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:157) at com.collaxa.cube.engine.CubeEngine._performActivity(CubeEngine.java:2585) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2444) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1121) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:322) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4497) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4428) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:685) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:116) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:153) at com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean.syncCreateAndInvoke(BPELEngineBean.java:107) 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.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105) at sun.reflect.GeneratedMethodAccessor756.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55) at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy175.syncCreateAndInvoke(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean_51369e_ICubeEngineLocalBeanImpl.syncCreateAndInvoke(BPELEngineBean_51369e_ICubeEngineLocalBeanImpl.java:911) at com.collaxa.cube.engine.delivery.DeliveryHandler.callCreateAndInvoke(DeliveryHandler.java:784) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:524) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:485) at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:164) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.request(CubeDeliveryBean.java:607) 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.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105) at sun.reflect.GeneratedMethodAccessor756.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:55) at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy172.request(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.request(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:829) at oracle.fabric.CubeServiceEngine.request(CubeServiceEngine.java:354) at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139) at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:179) at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:144) 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 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:59) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy185.request(Unknown Source) at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.doMessageProcessing(WebServiceEntryBindingComponent.java:1169) at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.processIncomingMessage(WebServiceEntryBindingComponent.java:768) at oracle.integration.platform.blocks.soap.FabricProvider.processMessage(FabricProvider.java:113) at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1160) at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:888) at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:561) at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:216) at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:179) at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:417) at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPost(FabricProviderServlet.java:480) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) 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:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592) 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:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) </message>

    So that means - only fault originating from invoke activity in BPEL can be associated with a fault policy. No other fault can be associated. Even if I throw a selectionFault from throw activity, that will not be captured. Only fault from invoke activity can be associated with a fault policy.
    Please confirm.
    Thanks,
    Edited by: 833944 on Feb 24, 2011 9:36 PM

  • Fault policies locaton and test xpath conditions not working.

    I cant place fault policies files in a non mds location or the composite directory.
    For example it does not work with an /opt/...... server path in the composite.xml property.
    Also, I can't get working xpath test expressions like this:
    <condition>
    <test xmlns:elem="http://na.telefonica.com/elementoscomunes">$fault.fault0/elem:AREA_ERROR/ErrorType = "F"</test>
    <action ref="reintentos-neon"/>
    </condition>
    In jdeveloper, the part is "fault0", and the subelements are like i've showed, but the condition never matches.
    I saw in a forum that the sintax was $fault.nameofpart/xpathexpression, but doesn't seem to work. I've tried lots of permutations of the syntax, and also with 'F' instead of "F".
    ¿Any Idea?

    This is the exception in the server GUI
    <fault>
    <bpelFault>
    <faultType>1</faultType>
    <OBA_Par_Alta_AveriaFault>
    <part name="fault0">
    <elem:AREA_ERROR>
    <ErrorID>8888</ErrorID>
    <ErrorType>F</ErrorType>
    <ErrorDesc>Afsafds</ErrorDesc>
    </elem:AREA_ERROR>
    </part>
    </OBA_Par_Alta_AveriaFault>
    </bpelFault>
    </fault>

  • A question regarding authorisation policies in OIM 11g

    Hi,
    I went through the list of OOTB Authorization policies in OIM 11g, just to know what all permissions were given to the 'ALL USERS' role which will be assigned to any OIM user by default.
    Below two policies are of a bit confusion to me. It would be great if you can put some light and clarify the missing link.
    ::::::::Role Management Role Owner Policy::::::
    This has the permission to delete role, modify role and search role:
    This is applicable to all roles in the system.
    This is assigned to 'ALL USERS' role.
    So as per my understanding, any user who is a member of ALL USERS role, can delete, modify and search role.
    But I can see only search role functionality for the default user. (ie., any user who is a member of 'ALL USERS' role)
    A simple user was not able to delete any kind of role.
    Is my understanding incorrect... Where is the missing link???
    :::::::User Management All Users Policy:::::::
    Permission is view user detail.
    Applicable to All users and assigned to 'ALL USERS' role.
    So any user should be able to view any other user detail.
    But its not happening. A user was not able to view another user's detail
    Is my understanding in correct... Where is the missing link???
    Looking forward to hearing from you,
    Many thanks in advance
    Warm regards,
    818343

    Can u check if role is assignd to user.

  • Using fault-policies with mediator and db Adapter doesn't work

    Please help! I'm stuck on this for 2 days....
    Hi Friends.
    In my project I am trying to give some treatment to an exception from a db adapter running a pl/sql procedure.
    I am forcing a raise_application_error in the procedure in order to treat the exception and I'd like the fault-police to treat it as "human-intervention".
    The db-adapter is wired to a mediator:
    jms-service ----> Mediator -----> Jca db adapter
    When I get the exception the log says:
    9d8bff56a1 due to: BINDING.JCA-12563[[
    Exception occured when binding was invoked.
    Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PersistirODS' failed due to: Stored procedure invocation error.
    Error while trying to prepare and execute the FORNECEDOR.UPSERTFORNECEDOR API.
    An error occurred while preparing and executing the FORNECEDOR.UPSERTFORNECEDOR API. Cause: java.sql.SQLException: ORA-20101: Deu Merda
    ORA-06512: at "FORNECEDOR.UPSERTFORNECEDOR", line 405
    ORA-06512: at line 1
    Check to ensure that the API is defined in the database and that the parameters match the signature of the API.  This exception is considered not retriable, likely due to a modelling mistake.  To classify it as retriable instead add property nonRetriableErrorCodes with value "-20101" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
    The invoked JCA adapter raised a resource exception.
    Please examine the above error message carefully to determine a resolution.
    and then it looks like it's trying to run some fault-police but it says:
    [2014-04-10T20:01:39.667-03:00] [AdminServer] [WARNING] [] [oracle.integration.platform.faulthandling] [tid: Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms\n] [userId: weblogic] [ecid: 11d1def534ea1be0:-1fa77a00:145468d59e7:-8000-000000000002801a,0] [APP: soa-infra]  [RejectedMsgHandling]Unable to apply policies on the rejected message with id - 60046[[
    oracle.fabric.common.FabricException: Cannot resolve binding to a fault policy [Faulted Activity Details:
    Activity Name=null
    Activity Id=null
    Activity lineNumber=null
    Reference Name=null
    WsdlLocation=null
    ActivityType=null
    Here are my fault-policies and fault-bindings files:
    <?xml version="1.0" encoding="UTF-8" ?>
    <faultPolicyBindings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                         xsi:schemaLocation="http://schemas.oracle.com/bpel/faultpolicy ../xsd/FaultBindings.xsd"
                         xmlns="http://schemas.oracle.com/bpel/faultpolicy">
    <composite faultPolicy="fault-policy"/>
    </faultPolicyBindings>
    <?xml version="1.0" encoding="UTF-8" ?>
    <faultPolicies xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                   xsi:schemaLocation="http://schemas.oracle.com/bpel/faultpolicy ../xsd/FaultPolicies.xsd"
                   xmlns="http://schemas.oracle.com/bpel/faultpolicy">
      <faultPolicy id="fault-policy">
        <Conditions>
          <faultName xmlns:medns="http://schemas.oracle.com/mediator/faults"
    name="medns:mediatorFault"  >
            <condition>
              <action ref="default-human-intervention"/>
            </condition>
          </faultName>
          <faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:PersistirODS">
            <condition>
              <action ref="default-human-intervention"/>
            </condition>
          </faultName>
          <faultName>
            <condition>
              <action ref="default-human-intervention"/>
            </condition>
          </faultName>
        </Conditions>
        <Actions>
          <Action id="default-human-intervention">
            <humanIntervention/>
          </Action>
        </Actions>
      </faultPolicy>
    </faultPolicies>
    Again
    Please help! I'm stuck on this for 2 days....

    Could you try specifying test element inside condition like the following one
        <faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:mediatorFault">
            <condition>
             <test>contains($fault.mediatorErrorCode, "AppropriateErrorCode")</test>
              <action ref="default-human-intervention"/>
            </condition>
          </faultName>

  • How to careate Fault Policies.xml file in J Developer.

    Hi Friends,
    I want to handle Mediator Exceptions for that i need to create fault policies.xml file and i am new for mediator..can you Explain How to create fault policies.xml in Jdeveloper ...May i know what's the steps to folllow.. and i refered http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/med_faulthandling.htm#BABBGIDE
    this link also but i didn't get from that..?

    There is no UI support to create fault-policies.xml. One has to create it manually based on the schema defined in the doc(the link you posted). You can see the sample file here - http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/med_faulthandling.htm#CHDFAEEF.
    -Sandeep

  • Fault policies not getting executed for called BPEL process

    Hi,
    I am facing one issue in execution of fault policy for a called BPEL Process.
    I have two BPEL Processes - BPELProcess1 and BPELProcess2.
    We have fault-policies and fault-bindings file.
    Case1 - BPELProcess2 is synchronous :-
    BPELProcess2 throws a fault of selectionFailure.
    Now this fault is defined in fault-policies and fault policy is bound to BPELProcess2 component in fault-bindings.xml file.
    But this fault policy is NOT getting executed.
    This selectionFailure fault from BPELProcess2 goes unhandled and in BPELProcess1, invoke activity gets this unhandled fault and raises a fault "remoteFault".
    This remotefault is also defined in fault-bindings and bound to BPELProcess1 component. Here fault policy bound to BPELProcess1 is working fine.
    So problem is that for called process, fault policies are not getting executed while for calling process, they are getting executed.
    Case1 - BPELProcess2 is Asynchronous
    BPELProcess2 is asynchronous. So same situation happening here. Fault policy for BPELProcess2 is not getting executed on throwing selectionFailure.
    But now here, since BPELProcess2 is async in nature, BPELProcess1 is not getting response and it is always waiting for response which is wrong.
    So how can we use fault policies in this case?
    Please suggest.
    Thanks & Regards,
    Parshant

    So that means - only fault originating from invoke activity in BPEL can be associated with a fault policy. No other fault can be associated. Even if I throw a selectionFault from throw activity, that will not be captured. Only fault from invoke activity can be associated with a fault policy.
    Please confirm.
    Thanks,
    Edited by: 833944 on Feb 24, 2011 9:36 PM

  • Can error handling framework use fault policies and BPEL catch blocks

    As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
    The problem we have experienced in our design is as follows:
    •     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
    •     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
    •     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
    The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
    It seems the two mechanisms "cannot play nicely together"

    As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
    The problem we have experienced in our design is as follows:
    •     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
    •     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
    •     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
    The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
    It seems the two mechanisms "cannot play nicely together"

  • Retry mechanism in Fault handling framework SOA 11g

    hi
    i have used Fault management framework in my project. I have added fault-policies and fault-bindings file. in fault-policies file i am using retry mechanism for any remote or binding fault. but i am not able to see the retry working in flow trace. however human intervention and terminate actions are working fine.
    can any one assist me why retry mechanism is not working.
    thanks in advance.

    hi
    thanks for the response. i added that property in my bpel tag but unfortunately it didn't work. plus the instance remains in running state. plz help me out with this.
    this is my fault-policies.xml and fault-binding.xml
    fault-policies.xml*
    <?xml version="1.0"?>
    <faultPolicies xmlns="http://xmlns.oracle.com/CreateTaskPOC_jws/Project9/BPELProcess1">
    <faultPolicy version="2.0.1" id="MyCompositeFaultPolicy">
    <Conditions>
    <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    name="bpelx:bindingFault">
    <condition>
    <action ref="ora-retry"/>
    </condition>
    </faultName><faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    name="bpelx:remoteFault">
    <condition>
    <action ref="ora-retry"/>
    </condition>
    </faultName>
    </Conditions>
    <Actions>
    <Action id="ora-rethrow-fault"><rethrowFault/></Action>
    <Action id="ora-retry">
    <Retry>
    <retryCount>3</retryCount>
    <retryInterval>2</retryInterval>
    <retryFailureAction ref="ora-rethrow-fault"/>
    </Retry>
    </Action>
    </Actions>
    </faultPolicy>
    </faultPolicies>
    fault-bindings.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <faultPolicyBindings version="2.0.1" xmlns="http://xmlns.oracle.com/CreateTaskPOC_jws/Project9/BPELProcess1">
    <composite faultPolicy="MyCompositeFaultPolicy"/>
    <component faultPolicy="MyCompositeFaultPolicy">
    <name>BPELProcess1</name>
    </component>
    <reference faultPolicy="MyCompositeFaultPolicy">
    <name>InsertEmp_BPELProcess</name>
    </reference>
    </faultPolicyBindings>

  • Facing issue while handling faults using fault-policies.xml

    Hi All,
    Scenario: One Asynchronous Bpel is trying invoke the webservice. When the status of the webservice is "Down", the BPEL will throw "System fault : remoteFault"
    This fault will be handled by the fault-policies.xml.
    CustomFaultHandler.java : basically it will print data to audit-trail and send data to the JMS Queue.
    I am facing some issues , when i am trying to handle faults using fault-policies.xml.
    Issue1: Display warning message at time of deployment : Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
    Issue2: CustomFaultHandler.java is able to print data to audit-trail but unable to send data to the Queue. and why the policy file getting executed at time of "Start of Invocation" and then it's showing "Invocation faulted" ?
    Audit-Trail Message:
    *===========*
    Started invocation of operation "process" on partner "RemoteService".Started invocation of operation "process" on partner "RemoteService".
    [Fault Recovery] Invoked handleBPELFault on custom java action class "com.CustomFaultHandler".
    Invoke1
    190002190002
    default/TestjavaAction!5.0*soa_fcb2a5dd-06a7-47f9-bb88-cab14d343856/TestBPEL
    190002
    Faulted while invoking operation "process" on provider "RemoteService". Faulted while invoking operation "process" on provider "RemoteService".
    fault-policies.xml:
    *==========*
    <?xml version="1.0" encoding="UTF-8"?>
    <faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
    <faultPolicy version="2.0.1" id="ErrorHandlingModelr"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://schemas.oracle.com/bpel/faultpolicy"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Conditions>
    <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    name="bpelx:remoteFault">
    <condition>
    <action ref="ora-java"/>
    </condition>
    </faultName>
    </Conditions>
    <Actions>
    <Action id="ora-java">
    <javaAction className="com.CustomFaultHandler"
    defaultAction="ora-terminate">
    <returnValue value="Manual" ref="ora-abort"/>
    </javaAction>
    </Action>
    <Action id="ora-abort">
    <abort/>
    </Action>
    </Actions>
    </faultPolicy>
    </faultPolicies>
    fault-bindings.xml:
    *===========*
    <?xml version="1.0" encoding="windows-1252" ?>
    <faultPolicyBindings version="2.0.1"
    xmlns="http://schemas.oracle.com/bpel/faultpolicy"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <component faultPolicy="ErrorHandlingModelr">
    <name>TestBPEL</name>
    </component>
    </faultPolicyBindings>
    Warning Message when trying to deploy the composite to the server :
    =============================================
    Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
    Error Message from server:
    *==============*
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.
    failure to handle a fault thrown from a scope, by any blocks in the scope chain.
    This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
    A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
    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: Fault not handled.
    failure to handle a fault thrown from a scope, by any blocks in the scope chain.
    This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
    A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
    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)
    Please help..
    Thanks in Advance
    Edited by: Sharmistha Ghosh on May 16, 2012 12:37 PM

    My SOA suite version is 11.1.1.7 and i was getting the same warning  while compiling the Composite in JDeveloper. To fix it update your fault-policy.xml
    Change it to
    <faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <faultPolicy version="0.0.1"
                     id="BPELProcessV1_Faults"
                     xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                     xmlns:xs="http://www.w3.org/2001/XMLSchema"
                     xmlns="http://schemas.oracle.com/bpel/faultpolicy"
                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    And it will solve the issue.

  • Mediator 11.1.1.5 faults Java Handler not getting called fault-policies

    Hi,
    I have a Oracle SOA 11.1.1.5 Mediator and am handling the faults using fault policies but somehow custom java handler is not invoked when an error occurs and this is what I see in the log but somehow my custom java handler class is not getting called.
    INFO: FaultPoliciesParser.parsePolicies ------->Begin Parsing of policy file
    <Apr 16, 2012 10:30:17 PM EDT> <Error> <oracle.soa.mediator.common.listener> <BE
    A-000000> <Enququeing to Error hospital successful...>Here is the fault-policies.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
      <faultPolicy version="2.0.1" id="medFaultHandling"
                   xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                   xmlns:xs="http://www.w3.org/2001/XMLSchema"
                   xmlns="http://schemas.oracle.com/bpel/faultpolicy"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <Conditions>
          <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
                     name="bpelx:remoteFault">
            <condition>
              <action ref="java-fault-handler"/>
            </condition>
          </faultName>
          <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
                     name="bpelx:bindingFault">
            <condition>
              <action ref="java-fault-handler"/>
            </condition>
          </faultName>
          <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
                     name="bpelx:runtimeFault">
            <condition>
              <action ref="java-fault-handler"/>
            </condition>
          </faultName>
        </Conditions>
        <Actions>
          <Action id="java-fault-handler">
            <javaAction className="com.mediator.faults.CustomMediatorFaultHandler"
                        defaultAction="ora-human-intervention" propertySet="myMediatorProps">
              <returnValue value="OK" ref="ora-human-intervention"/>
            </javaAction>
          </Action>
          <Action id="ora-human-intervention">
            <humanIntervention/>
          </Action>
          <Action id="ora-rethrow-fault">
            <rethrowFault/>
          </Action>
          <Action id="ora-retry">
            <retry>
              <retryCount>3</retryCount>
              <retryInterval>15</retryInterval>
              <exponentialBackoff/>
              <retryFailureAction ref="java-fault-handler"/>
            </retry>
          </Action>
        </Actions>
        <Properties>
          <propertySet name="myMediatorProps">
            <property name="logFileName">mediator-faults.log</property>
            <property name="logFileDir">C:/software</property>
          </propertySet>
        </Properties>
      </faultPolicy>
    </faultPolicies>Here is my the fault-bindings.xml:
    <?xml version="1.0" encoding="UTF-8" ?>
    <faultPolicyBindings version="2.0.1"
                         xmlns="http://schemas.oracle.com/bpel/faultpolicy"
                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <composite faultPolicy="medFaultHandling"/>
    </faultPolicyBindings>And here is the snippet of composite.xml where I put the below properties:
    <component name="Router">
        <implementation.mediator src="Router.mplan"/>
        <property name="oracle.composite.faultPolicyFile">fault-policies.xml></property>
        <property name="oracle.composite.faultBindingFile">fault-bindings.xml></property>
      </component>But when the exception occurs I don't see my custom Java Handler being invoked. As I created a jar file and placed it in
    *<Middleware_Home>\Oracle_SOA1\soa\modules\oracle.soa.mediator_11.1.1*
    and updated oracle.soa.mediator.jar manifest by putting the path of the jar file. Restarted the servers but still when an exception occurs in Mediator custom java handler is not invoked. Any ideas what I am missing or are there any special steps
    Thanks

    There is no point in retry on binding fault, rather you can raise it as exception and catch it in sepcific catch block or catch all will handle it.
    Ideally this particular instance will be faulted and if required you can customize to send a mail with fault string to developer or support person or dba
    This type of fault need human intervension to fix this code or it could be data issue.
    - It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
    Thanks,
    Vijay

  • Mediator Exception Handling without fault policies

    Hi,
    Could somebody help me on defining exception handling to MEDIATOR component?
    Is there is a way where we can do this without using the fault policies?
    Thanks,
    SV.

    Business faults are application-specific and are explicitly defined in the service WSDL file. You can handle business faults by defining the fault handlers in Oracle JDeveloper at design time. System faults occur because of some problem in the underlying system such as a network not being available. Oracle Mediator provides fault policy-based error handling for system faults.http://docs.oracle.com/cd/E21764_01/integration.1111/e10224/med_faulthandling.htm
    Regards,
    Anuj

Maybe you are looking for

  • How can i print just one page of photo book without printing the entire book

    how can i print just one page of photo book without printing the entire book

  • CS4 Flash. First attempt to save a file creates an unknown error.

    I bought CS4 when I bought my first Mac.  I started building an inventory of production software but had only used Photoshop and Adobe.  I tried to do my first Flash project today and following a tutorial, I tried to save the initial file and it erro

  • I am running mail 3.6 and brushed the touchpad...

    ...., causing the display to go from split (top lists messages, bottom displays hilighted message) to message list only.  I can't figure out how to switch it back. Any help appreciated.

  • Sorry, this is not a forms question

    Hi, Sorry to ask this question here, but i've no options left. I dont have google access in the office. Just if someone had done something like this. Is it possible to generate a excel file from a word doc or vice versa? Like if i have 2(1by2) table

  • Connect to xbox live??

    I'm having a difficult time connecting my x box to my router. I have called x box support and apple support with no luck. Apple says it could be port mapping but x box did not give me a port . Has anyone resolved this issue??