Fault Handling in BPEL process

hi
We have to develop an application which involves several BPEL processes and proxy service(OSB) and JMS queue etc.
What is the difference between Fault Management Framework in SOA11g and normal fault handling(using catch and throw activities)?
which one we should prefer for fault handling in our application n why?
Plz help thanks in advance.

Hi-
In Normal Fault handling process, you will be able to catch the faluts only but in Fault Management Framework if a fault occurs the framework catches the fault and performs a user-specified action defined in a fault policy file associated with the activity. You can also have a human intervention prescribed in it, where you perform recovery actions from Enterprise Manager.
Pls go throgh the below post for detailed description
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_faults.htm
Fault Management Framework and non BPEL soap faults
Edited by: 333333 on Mar 23, 2011 5:01 PM

Similar Messages

Fault Handling in BPEL

Hi,
Can anyone explain me how do I handle the faults in my BPEL process. What I want to do is whenever any Faults occur in my Invoke activity I want to capture the error messages and send an email to myself with the error messages. Appreciate if anyone can help me out here with the design process. I'm new to BPEL and if there is any step by step design document it would really help me.
Thanks
-Prapoorna

Please read
http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/faults.htm#sthref1186

Fault information from bpel process when exception happens

How to extract all the fault information from bpel process when exception happens?
Are there any other methods other than "ora:getFaultName(), ora:getFaultAsString()"
When I use "ora:getFaultName(), ora:getFaultAsString()", I get the below message,so I am wondering whether
I can get any more information about the exception as mentioned below - "detailed root cause described in the exception message" -> how do I get it?
Check the detailed root cause described in the exception message text and verify that the XPath query is correct.

Hi,
As far as I know, it's not possible to get the exception message with a catch all. You need to catch each exception separately, and the you will be able to get each message.
Regards
Gustavo

Implement custom fault handling in bpel

Hi,
Can you please provide some link on how to implement custom fault handling in bpel
Thanks,
kpr

See the article below for details on implementing custom fault handling.
http://beatechnologies.wordpress.com/2011/07/18/fault-handling-in-oracle-soa-suite-advanced-concepts/

Trying to throw fault from one BPEL process to another

We are trying to throw a fault from one BPEL process to another and apparently are experiencing a common problem. That is, the invoking process times out and never receives the fault.
Likely a beginner's mistake is at fault (pun intended).
Below are samples of a simple "Hello World" process that tries to throw the fault.
snippet of pbel file....
<process name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://helloworldjavaproject/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<faultHandlers>
<catchAll>
<sequence name="Sequence_1">
<assign name="Assign_3">
<copy>
<from expression="12345"/>
<to variable="FaultVar" part="code"/>
</copy>
<copy>
<from expression="'Hello fault summary'"/>
<to variable="FaultVar" part="summary"/>
</copy>
<copy>
<from expression="'Hello test detail'"/>
<to variable="FaultVar" part="detail"/>
</copy>
</assign>
<throw name="Throw_2" faultName="client:myFault"
faultVariable="FaultVar"/>
</sequence>
HelloJavaWorldSynchronous.wsdl file
<definitions
name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl";/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous" schemaLocation="HelloJavaWorldSynchronous.xsd";/>
</schema>
</types>
<message name="HelloJavaWorldSynchronousRequestMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessRequest"/>
</message>
<message name="HelloJavaWorldSynchronousResponseMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessResponse"/>
</message>
<portType name="HelloJavaWorldSynchronous">
<operation name="process">
<input message="client:HelloJavaWorldSynchronousRequestMessage"/>
<output message="client:HelloJavaWorldSynchronousResponseMessage"/>
<fault name="myFault" message="ns1:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="HelloJavaWorldSynchronous">
<plnk:role name="HelloJavaWorldSynchronousProvider">
<plnk:portType name="client:HelloJavaWorldSynchronous"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
The standard RuntimeFault.wsdl file (RuntimeFaultMessage message is defined in here, so I don't need a message in HelloJavaWorldSynchronous.wsdl. Do I?)
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
But when we invoke the process, after the standard 45 seconds timeout, we still get...
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is f290d62d2ad31aa6:-49eb76f4:124eb51622a:-7c91. Please check the process instance for detail.</faultstring>
</Fault>
The console audit below might hold a clue. I noticed the mesage BPELFault" has not been caught by a catch block at the end.
<catchAll>
<sequence>
Assign_3
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</FaultVar>
Throw_2 (faulted)
[2009/11/13 11:18:32] "{http://xmlns.oracle.com/HelloJavaWorldSynchronous}myFault" has been thrown. More...
-<myFault xmlns="http://xmlns.oracle.com/HelloJavaWorldSynchronous">
-<part name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</myFault>
</sequence>
</catchAll>
[2009/11/13 11:18:32] "BPELFault" has not been caught by a catch block.
[2009/11/13 11:18:32] BPEL process instance "570162" cancelled

Thanks very much for this answer. It was right on.
You wanted to know "how (I) get on". Funny you should ask. Believe it or not, I had figured out the problem on my own just about the time you were posting your reply (of course, this is a bit too convenient. No one will ever believe me).
But the answer leads to another question. What is the Throw activity for, if not to throw an error to the calling process? Is it only used to throw within scope of the process its self?
I am probably biased by the Java world I am coming from, but Throw feels like it should terminate the process (without side effects like a big red mark in the console) bubble up the fault to the calling process who can catch it (if so desired). Using the reply we must explicitly Terminate (which includes that unsightly red mark).
Is there any way to get this behavior from the Throw, or should we just reprogram the "wetware" and learn a new paradigm?
Is there any way to end a process without marking it with a red flag that suggests something went wrong?

How to implement Fault Handler in BPEL

Any good material or sample available on ? How to handle exception properly If error does occur in BPEL ?

Hi',
Check this out,
http://rathinasaba.wordpress.com/2011/05/29/fault-handling-in-bpel/
http://rahullahiri.blogspot.com/2011/02/basic-fault-handling-in-soa-11g.html
http://jianmingli.com/wp/?p=2708
-Yatan

Fault Handling in BPEL - Continue after Catch Block

Hi,
I have a catch block in my BPEL process.
On exception, the catch block catches the error and terminates the BPEL Process.
Is it possible to loop back the flow after the catch sequence?
Thanks,
Venkat

Hi,
Thanks for your reply
Sorry, I was not clear with my question.
I have a infinite loop in my process. Inside the loop I have an invoke operation(Invokes another BPEL process) and a wait operation. If any exception occurs, my BPEL process terminates. However, I wanted my BPEL process to just continue in the loop.
I solved the issue with the help of this How to handle fault when BPEL process is polling a FTP server which is down
i.e, using the Scope activity. Place my invoke operation inside a scope and put a catchAll block only for that scope. Its working fine
Thanks,
Venkat

Fault handling using BPEL

Good, I'm working on a research project and I have been assigned the task of processing errors in SOAP BPEL.
I've been searching on Internet and the most commonly methodology used is soap-fault with throwing and catching exceptions in BPEL process.
I wonder if I can do it in a more proactive and comprehensive way, catching those exceptions through a web service, and if possible, how can the BPEL process send the information encapsulated in the soap-fault to the web service?
If there is another way of treating errors or someone can suggest me another way, I would be very grateful.

I am not clear on your objective, but in so far as BPEL SE Component of Open-ESB Project, running on JBI is concerned you can read more about Fault handling and other features of BPELSE here at http://wiki.open-esb.java.net/Wiki.jsp?page=BPELSE. Also, you can find some working examples on this page http://wiki.open-esb.java.net/Wiki.jsp?page=HowToDo
- Malkit

Fault handling in sync process

Hi,
In my synchronous BPEL process I have a parallel flow with 3 parallel calls to web services,
I want to add a fault catch if one of the services is not responding.
So that if I got a response from 2 of the web services, but the third one is down, I can continue the process and assign something instead of the 3rd ones output.
How can I do this ?
Thanks!

-Catch may be used if you know what exceptions are being thrown by the web service.
-One of the worst (:)) things can be if the web service is down, so you should put that logic in the catchall.
-Under the logs .... bpel/opmn/logs/*bpel* log. This is the log where you can see whats happening in the BPEL process. And if some error occured while invoking the web service.

Fault Handling in Asynchronous process

Hi,
I want to know how to throw fault from an Asynchronous process to the calling process. In a synchronous process we generally throw faults using fault message in 'process' port type. But Im not sure how to throw a fault from Asynchrnous process to the calling process that can be caught in the catch block of the calling process.
Can some one update me with the feasibility of this.
Thanks,

Hi,
Look inside the Oracle® BPEL Process Manager Developer's Guide at http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/faults.htm#BABIBAFC
8.8.2 Returning a Fault in an Asynchronous Interaction
In an asynchronous interaction, the client does not wait for a reply. The reply activity is not used to return a fault. Instead, the BPEL process returns a fault using a callback operation on the same port type that normally receives the requested information, with an invoke activity.
Example
    <portType name="BPELFaultHandling">
        <operation name="initiate">
            <input message="client:BPELFaultHandlingRequestMessage"/>
        </operation>
    </portType>
    <portType name="BPELFaultHandlingCallback">
        <operation name="onResult">
            <input message="client:BPELFaultHandlingResponseMessage"/>
        </operation>
        <operation name="onError">
            <input message="client:BPELFaultHandlingErrorMessage"/>
        </operation>
    </portType>On the caller side you have to use one invoke followed by a pick activity waiting for onResult or onError callback.
Best Regards,
Harald Reinmueller

An issue with BPEL fault handling

Hi,
I need to catch an exception in my BPEL process. The exception is thrown from a partner service(in java). I am using the catch fault handler in BPEL to catch a specific fault.
1. When I give "systemFault" as the faultName its catching the fault
2. But when I give "Exception" as the faultName its not catching the fault
In the second case server log gives me the following fault,
BPCOR-6135:A fault was not handled in the process scope; Fault Name is {......
Can you please help me to figure out the problem here.
Please let me know if you need any more information.
Thanks in advance,
Jose John

Thank you very much for your reply.
Following is the wsdl file,
relevant part of the WSDL file
<message name="Exception">
<part name="fault" element="tns:Exception"/>
</message>
<portType name="PostConstraintChecker">
<operation name="check">
<input message="tns:check"/>
<output message="tns:checkResponse"/>
<fault message="tns:Exception" name="Exception"/>
</operation>
</portType>
<binding name="PostConstraintCheckerPortBinding" type="tns:PostConstraintChecker">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="check">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
<fault name="Exception">
<soap:fault name="Exception" use="literal"/>
</fault>
</operation>
</binding>
Is this correct? Do you see any problems in this? Please let me know if you need any more information which will help you in debugging the issue.
Thanks,
Jose John

11g: Help regarding fault handling framework

I am trying to implement a POC demonstrating the fault handling framework using fault policies. I am trying to handle remote and business faults. These faults are being thrown explicitly in the code. But I dont see the framework coming into picture. Here are the fault policies and fault bindings files
The POC does the following
1. If input is R, throws a remote fault.
2. If input is B1, throws a business fault. There is a catch defined for this. But as we also have a policy for this error, we expect the policy overrides the catch
3. If input is B2, throws a business fault. There is no catch defined for this. We expect the policy to handle this.
4. If any other input, we return a string.
<?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="2.0.1" id="ComponentFaults"
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-human-intervention"/>
</condition>
</faultName>
<faultName xmlns:ns1="NS_B1"
name="ns1:LP_B1">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
<faultName xmlns:ns2="NS_B2"
name="ns2:LP_B2">
<condition>
<action ref="ora-human-intervention"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
Here is the fault-bindings.xml file
<?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">

<component faultPolicy="ComponentFaults">
<name>BPEL</name>
</component>
</faultPolicyBindings>

I created another bpel in the same composite that calls the original bpel. So now, those errros are supposed to travel to calling bpel.
Fault policies are coming into effect now. So, one part of the problem is solved, that atleast syntax and all is correct, and the fwk does work (!) but another one has opened - why is the fault not getting handled by the fwk if there is a single bpel that is throwing and not catching those faults.
Also, even in this new avatar, fault b1 is getting handled by the catch in BPEL process, while the fault policies are supposed to override any catches in bpel code.
What I was attempting was, throwing the fault in a bpel process and expecting the fault handling fwk to handle it.
It turns out, the framework is not capable of doing this, its only capable of handling faults coming after an invoke activity.
Consulted Oracle Support on this. Their response
The behavior within the single composite you are seeing is correct and is by design. As the documentation states:
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_faults.htm#BABIGGIB
If a fault occurs during runtime in an invoke activity in a process, the framework catches the fault and performs a user-specified action defined in a fault policy file associated with the activity.
The fault management framework catches all faults (business and runtime) for an invoke activity.
So the above means that unless the fault is thrown in response to an invoke activity the Fault Policy set will not be triggered, which has been confirmed through the test you have uploaded. Please let me know if you have any questions or concerns.

Query on Fault Handling in SOA 11g

Hi All,
I have created a BPEL process which polls a DB table and does a logical delete(updates status column as read). Now I wanted to rollback the update incase of any fault in the BPEL process. I have an email activity and an audit table entry in my catch/catch-all blocks.
1. If I don’t add any error handling code to BPEL, the transaction (update to DB) is rolled back incase of fault
2. If I add any error handling code to BPEL, the transaction (update to DB) doesn’t get rolled back incase of fault.
3. If I add bpelx:rollback in my catch/catch-all blocks, the transaction (update to DB) gets rolled back but I am unable to send email/add audit entries as those get rolled back too.
4. I created a new datasource which supports local transactions and configured the Auditing to make use of this datasource. Now in this case when bpelx:rollback happens incase of fault, transaction (update to DB) gets rolled back and Audit data is also added (since it’s a separate transaction and not part of the Global transaction). However email activity still doesn’t get sent as it is rolled back as well.
Please let me know how do I handle this scenario where incase of rollback both Auditing as well as email should work.
Regards
Subhankar

Hi,
The email activity basically invokes a notification service(partner link/reference). Can we set the below properties at the reference section ?
<property name="bpel.config.oneWayDeliveryPolicy" many="false" type="xs:string">sync</property>
<property name="bpel.config.transaction" many="false" type="xs:string">requiresNew</property>
Or do these properties need to be set at the BPEL process service component section in the composite.xml file only. I tried setting at reference level, however it isnt taking effect. Basically I am trying to have the email activity(notification service) as a separate transaction.
Thanks
Subhankar

Recover BPEL Process that crashed with OutOfMemoryError: PermGen space

Hello,
I'm running a Oracle 10G Soa Suite (10.3.5.0) on linux (x64).
Yesterday the oc4j soa instance got out of PermGen memory.
I Restarted the server, but one of the running processes gave a OutOfMemoryError (error attached at end).
I went to Administration tab on BPEL Console and in Recover (Callbacks) i found the instance that gave the error.
I recovered it, but it remain the same.
Can anyone help me on how to recover the process instance, if it is possible to recover it.
Thanks
Pedro
[2010/09/06 17:10:38] There is a system exception while performing the BPEL instance, the reason is "PermGen space". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point. less
<message>
java.lang.OutOfMemoryError: PermGen space
     at java.lang.String.intern(Native Method)
     at oracle.xml.parser.schema.XSDBuilder.parseElement(XSDBuilder.java:1310)
     at oracle.xml.parser.schema.XSDBuilder.parseCompositor(XSDBuilder.java:3040)
     at oracle.xml.parser.schema.XSDBuilder.parseComplexContent(XSDBuilder.java:2342)
     at oracle.xml.parser.schema.XSDBuilder.parseComplexType(XSDBuilder.java:1897)
     at oracle.xml.parser.schema.XSDBuilder.parseElement(XSDBuilder.java:1404)
     at oracle.xml.parser.schema.XSDBuilder.parseTopLevelElems(XSDBuilder.java:1013)
     at oracle.xml.parser.schema.XSDBuilder.buildSchema(XSDBuilder.java:824)
     at oracle.xml.parser.schema.XSDBuilder.parseIncludeAndImport(XSDBuilder.java:1260)
     at oracle.xml.parser.schema.XSDBuilder.parseTopLevelElems(XSDBuilder.java:1033)
     at oracle.xml.parser.schema.XSDBuilder.buildSchema(XSDBuilder.java:824)
     at oracle.xml.parser.schema.XSDBuilder.parseIncludeAndImport(XSDBuilder.java:1260)
     at oracle.xml.parser.schema.XSDBuilder.parseTopLevelElems(XSDBuilder.java:1033)
     at oracle.xml.parser.schema.XSDBuilder.buildSchema(XSDBuilder.java:824)
     at oracle.xml.parser.schema.XSDBuilder.build(XSDBuilder.java:454)
     at oracle.xml.jaxb.JaxbValidator.getNextSchema(JaxbValidator.java:338)
     at oracle.xml.jaxb.JaxbValidator.validate(JaxbValidator.java:185)
     at oracle.bpel.services.common.util.AbstractJaxbUtil.schemaValidate(AbstractJaxbUtil.java:196)
     at oracle.bpel.services.workflow.metadata.impl.TaskMetadataCache.getTaskDefinition(TaskMetadataCache.java:248)
     at oracle.bpel.services.workflow.metadata.impl.TaskMetadataService.getTaskDefinition(TaskMetadataService.java:198)
     at oracle.bpel.services.workflow.task.impl.TaskService.initiateTask(TaskService.java:257)
     at oracle.bpel.services.workflow.task.impl.TaskService.initiateTask(TaskService.java:225)
     at oracle.bpel.services.workflow.task.ejb.TaskServiceBean.initiateTask(TaskServiceBean.java:38)
     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.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)
</message>
Edited by: user4285739 on 7/Set/2010 4:22
Sorry. Wrong forum.

5.4 Resolving Out-of-Memory Errors in the BPEL Runtime Console at http://download.oracle.com/docs/cd/E14101_01/doc.1013/e15355/maint.htm#CHDCAAHE
5.6.6 PermGen Out-of-Memory Error During Deployment at http://download.oracle.com/docs/cd/E14101_01/doc.1013/e15342/bpelrn.htm#BABCEFJG
Regards,
Anuj

Fault handling policy for a process in the fault-binding.xml

Can I specify a fault handling policy for a specific process using fault handling framework 10.1.3.3?
<process faultPolicy="DefaultPolicy"/>
I cannot specify the name of the process according to the xsd :(
Can this be achieved?
I have a two different partner links in different processes having the same name. If I add the partner link to the fault-binding.xml what would be the result?
Note: I cannot use bpel.xml to specify the fault policies as of now.

The fault policy bindings file does not allow you to specify a specific fault policy for an individual processes. You can only do this for all BPEL processes (eg: process Level) or at finer grained levels such as partner link levels.
You might be able to use the partner link level for any services that call the process in which you wnat to error handle (eg: Process C needs to be error handled. Process A and B call C so for the partner link names for invoking C could have the fault policy defined for them). Therefore any faults returned from C could propagate back to process A / B and be handled within by the policy outside of Process C. Obviously if this apporach was used you would not want to use process level definitions as C would continue to use this.
If the partner links were of the same name, they should both be handled by the fault policy that is defined withiin the Fault policy (e.g Partner Link level definitions)
An approach that can be used is to specify the fault policy within the bpel.xml file. The information would be added as follows:
</partnerLinkBindings>

<faultPolicyBindings>
<process faultPolicy="AProcessFaultPolicy"/>
<partnerLink faultPolicy="APartnerLinnkPolicy">
<name>insertSSN_dbAdapter</name>
<name>Another_Adapter</name>
</partnerLink>
</faultPolicyBindings>

</BPELProcess>
</BPELSuitcase>
However, I noted you said you were unable to do this. I wasn't sure if this was for technical/governamce reasons or knowledge reasons (unsure where to place to the details.
Hope that helps and does not confuse matters
Dave

Fault Handling in BPEL process

Similar Messages

Maybe you are looking for