Throw customised Faults in BPEL

Hi ,
I need to throw a user-defined fault from my BPEL Process.How can I acheive that.When my BPEL process is called by other service it throw that specific fault.
Any documentation would also be of great help.
Thanks
Deepthi

I am using 10.1.3.1 Bpel Process Manager.
I am throwing the fault but on the console i am receiving an receive time out exception.Instead of the fault which I have thrown.
Thanks
deepthi

Similar Messages

Throwing a fault from an asynchronous bpel process

Hi,
can anyone please let me know how i can throw a fault to the calling client from an asynchronous bpel process?
(synchronous bpel uses the fault of the reply activity to do the same - i want a similar thing in a callback-invoke of an asynchronous process or any other way to do it if at all)
please let me know if it is possible becoz it was a requirement put forward by a customer and i just want to develop a proof of concept to the same.
regards,
pavan.

Hi,
I'm using BPEL process manager for calling a asynchronous web service,I can invoke the service from BPEL and the service is invoked correctly,but when I view the business process flow in BPEL Console my process is stopped at receive state and doesn't pass it.
Could anybody tell me if any thing should be set to receive a callback from an asynchronous web service to BPEL process?
Is it true that BPEL process receives a callback automatically (using a callback operation which I defined in my web service WSDL) on the same port type that normally receives the requested information, with an invoke activity?
So what could be wrong with my process or invoked web service that the BPEL process doesn't get any reply from my web service and remains in receive activity?
Thnx in advance,
Nasim

Issue in propagating the fault in BPEL

Hi,
I have an issue in propagating the fault in BPEL.
This is the scenario,
a) I have a BPEL process which inserts data to a table, where a column is a primary key.
b) I invoke this BPEL as a partner link in another BPEL process.
c) I have provided catch for primary key violation in the invoking BPEL process.
Here, it throws below remote fault:
When invoking locally the endpoint 'http://localhost:7777/orabpel/default/InsertExceptionGen/1.0', ; nested exception is:
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is bpel://localhost/default/HandlingESBFaultInsert1~1.0/20502-BpInv0-BpSeq1.6-2. Please check the process instance for detail.
But In the case of ESB, I could able to handle the primary key violation fault.
ie)
a) An esb process inserts data into a table, where a column is a primary key.
b) A BPEL process invoke this esb as a partner link.
c) In the invoking BPEL process, provided catch for primary key violation.
Pls. someone throw some light on this.
Thanks
Jude.

BPEL process should get a bindingFault for any application related errors.
since it received remote fault, may be some problem with connectivity.check the timeout values in the bpel configuration.

Customize faults in bpel.

When we use custom faults in bpel we get as follows:
<Faulthttp://xmlns.oracle.com/BPEL4http://schemas.xmlsoap.org/soap/envelope/>
<faultcode>client:BusinessFault</faultcode>
<faultstring>business exception</faultstring>
<faultactor>cx-fault-actor</faultactor>
<detail>
<BPEL4faultMessagehttp://xmlns.oracle.com/BPEL4>
<Code http://xmlns.oracle.com/BPEL4>9710</Code>
<Summary http://xmlns.oracle.com/BPEL4>Invalid xml document. According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.a: Invalid content was found starting with element 'ns1:input1'. One of '{"http://xmlns.oracle.com/BPEL4":input}' is expected. Please make sure that the xml document is valid against your schemas. </Summary>
</BPEL4faultMessage>
</detail>
</Fault>
That is whatever our custom fault structure is defined in bpel it comes under the detail tag as above.
Is there a way we can customise that by replacinh the code in the faultcode and summary in the faultstring tag so that we have the fault structure as
<Faulthttp://xmlns.oracle.com/BPEL4http://schemas.xmlsoap.org/soap/envelope/>
<faultcode>9710</faultcode>
<faultstring>Invalid xml document. According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.a: Invalid content was found starting with element 'ns1:input1'. One of '{"http://xmlns.oracle.com/BPEL4":input}' is expected. Please make sure that the xml document is valid against your schemas. </faultstring>
<faultactor>cx-fault-actor</faultactor>
<detail>
<BPEL4faultMessagehttp://xmlns.oracle.com/BPEL4>
<Codehttp://xmlns.oracle.com/BPEL4>9710</Code>
<Summaryhttp://xmlns.oracle.com/BPEL4>Invalid xml document. According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.a: Invalid content was found starting with element 'ns1:input1'. One of '{"http://xmlns.oracle.com/BPEL4":input}' is expected. Please make sure that the xml document is valid against your schemas. </Summary>
</BPEL4faultMessage>
</detail>
</Fault>

oops... sorry... I had typed it in as there is no way to copy that 'error message' on to the clipboard from the BPEL FLOW depiction.
it must have read 'HealthCareWorkFlowProcessRequest'...
the problem is not with the typo... :(
Am not able to find the root cause... but the flow fails when invoked from my web application...

Throwing custom faults

Hi,
I'm trying to catch timeouts and throwing a fault myself, so I can generify all kinds of exceptions into one fault. The problem is, even though I specify my throw as follows :
<throw name="Throw_Fault" faultName="client:InvocationException" faultVariable="fault"/>
the bpel service still returns
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">INT-CRO-ADMIN</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
In my wsdl I defined something like this:
<message name="InvocationException">
<part name="body" element="geo:ExceptionReport"/>
</message>
<portType>
<input msg ... />
<output msg ... />
<fault message="client:InvocationException"/>
</portType>
If I look at the instance flow, I see that the fault is catched correctly, and my own fault element is being created, but it seems as if bpel catches my fault again and throws a service.userException ...
How can a client receive my custom fault?

I am also facing the same problem did you find any solution.
If so can you please share it with me.

How to throw a fault in ESB?

Hi,
Is it possible to throw a fault in the ESB, for example in the following scenario?
I have a ESB-service consisting of a DB-adapter querying the database and a routing service connected to that adapter. Instead of letting the bus return an empty collection when no records are found, I like to throw a fault when the query returns "No records found".
Does anyone have a clue if this is possible in 10.1.3.3.1 and how?
Kind regards,
Harm

This is not possible. Or you must use a PL/SQL package, that you access from ESB, that throws an error.
Or use BPEL.
Marc
http://orasoa.blogspot.com

Logging the Runtime Fault messages BPEL in WLS logs

Requirement: I need to capture the run time fault from BPEL processes in the WLS logs how to do this?
Solution: I have tried following I created the Java class ot initialise the Java logging.
Java snippet:
private static final Logger logger = Logger.getLogger("oracle.soa.Logger");
static {
LogFormatter.configFormatter(logger);
public static final void log(String message) {
logger.log(Level.INFO, message);
In my BPEL process I have the CatchAll activity
In the ‘AssignFault I’ have the assignments using ora: getFaultAsString() , but I’m not getting the expected fault in Assign Activity which we see in Audit Trail.
In Audit Trail i see the following message against the my Validate Activity
"Invalid data: The value for variable "ReceiveXML_Read_InputVariable", part "body" does not match the schema definition for this part Element 'TimeBandList' not expected.. The invalid xml document is shown below:"
The ora: getFaultAsString() is showing the "com.oracle.bpel.client.BPELFault: faultName: {{http://docs.oasis-open.org/wsbpel/2.0/process/executable}invalidVariables} messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}"

I had gone thru that documentation. I needed something more than that.
Well, I want to know what entries go into the access log & what into custom
log of ours.
Actually, the entries with 200 status only are going into our custom log ,
how can I make the entries with status 302 (redirection) to get into the
custom log?
Thanks.
priya
Robert Patrick wrote:
Yes. http://www.weblogic.com/docs51/admindocs/http.html#logs
Priya Bangara wrote:
Hi,
Our company has WebLogic Server 5.0 b2 running on our livesite. They
have been using WLS's access log and their own custom log. Now, they
have found some problem with the logs and I'm looking into it.
I don't find any documentation on 5.0b2 on BEASYS's site anymore. Are
all the features like 'extended log format', 'log rotation' of WLS 5.1
were there in 5.0 b2 ?
Please help. Issue is very critical. I would appreciate if you could
also send me some links where I can find more info on WL's logging
mechanism.
Thanks in advance,
Priya

Is it possible to throw another Fault from Fault Policy handler Java Class?

Hi,
I am using SOA Suite 11g. My requirement is to catch any Fault that occurs in BPEL in the Fault Policy java handler, and then throw back another Fault (Which i want to create from the java class hander) by setting the Fault Part and other Fault details.
I will be getting the Fault message and code etc for different kinds of faults from a .properties file.
I tried creating a new BPELFault inside the handleFault method...
BPELFaultRecoveryContextImpl bpelCtx = (BPELFaultRecoveryContextImpl) ctx;
QName qName = new QName("http://xmlns.oracle.com/Application1_jws/FMF_Demo/FaultHandlerDemo","GenericFault");
BPELFault flt = new BPELFault(qName);
flt.setFaultName(qName);
flt.setPart("<faultPartName>","Fault Message Text...");
bpelCtx.setFault(flt);
The new Fault is thrown back to the BPEL process, but i am not able to get the Fault details within the catch block (for GenericFault) that i have set in the Java Handler.
Any help regarding this is highly appreciated.
Regards,
Shreyas

Has anybody come across this issue? Please help.
Regards,
Shreyas

Propagate fault from BPEL to BPM

This is what my use-case is - I have my BPM business process, from which I am calling my more granular BPEL processes. In case of a fault occurring in the BPEL level, I want to propagate that fault to the BPM level, so I can pick the fault, and handle it there, either by creating a sub process, or terminating the BPM process, or whatever else.
So far, I have not had any success in sending the faults from the BPEL to the BPM. If you done done something like this, please help me on how to proceed.
Any help/inuts greatly appreciated.
Thanks,
Abhi

First you need to be sure the WSDL for your BPEL is defining the faults that it can return. Next you need to be sure to throw the proper fault from the BPEL process.
You could confirm that is working using EM or SoapUI to test your BPEL service.
Once that is working you can use a border exception event on the service activity in the BPMN process to catch the fault that you have declared in the BPEL WSDL.
Thanks,
Adam DesJardin

Fault handler BPEL PM Weblogic issue ?

Products:
SOA for WebLogic Server (10.1.3.4) , p7490612_101340_GENERIC
Jdeveloper 10.1.3.4
Windows XP sp2
1.- I was install SOA for WSL 9.2 and Jdev succesfull, now i start with any test.
2.- I test Fault handling framework , then i create the simple xml files: fault-bindings.xml and fault-policies\mybpiPolicy.xml
----- Abstract files
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
<condition>
<action ref="ora-retry"/>
</condition>
</faultName>
<Action id="ora-retry">
<retry>
<retryCount>2</retryCount>
<retryInterval>6</retryInterval>
<exponentialBackoff/>
<retryFailureAction ref="ora-human-intervention"/>
</retry>
</Action>
3.- Then i create an simple async BPEL case for fault handling with a DB BPEL Adapter using a wrong Jdbc string for instance Bad SID database (deliberately , The correct is XE not XE1).
Then i test it, and with audit trail in BPEL Console, i can view the 2 retries that i indicate in the descriptor, but after [FAULT RECOVERY|http://forums.oracle.com/forums/] Marked Invoke activity as "pending manual recovery, it have a exception.
* In normal case with OC4J, after last line, the process is ready for recovery in a manual step.
* Well i think so maybe i missing another configuration or parameter because it is deploy in WebLogic, i do not. next i put the text that in audit trail appers.
Please help, regards.
----- my Messages in audit trail.
--2008/12/30 21:28:29-- [FAULT RECOVERY|http://forums.oracle.com/forums/] Marked Invoke activity as "pending manual recovery".
--2008/12/30 21:28:30-- "BPELFault" has not been caught by a catch block.
--2008/12/30 21:28:30-- There is a system exception while performing the BPEL instance, the reason is "faultName: {{[http://schemas.oracle.com/bpel/extension]}remoteFault} messageType: {{[http://schemas.oracle.com/bpel/extension]}RuntimeFaultMessage} parts: {{code=0 ,summary=file:/D:/oracle/soasuitebasic/bpel/domains/default/tmp/.bpel_Test1BPEL_1.0_7f0af90c7bf1874b5077831987befd2d.tmp/do.wsdl [ do_ptt::doSelect(doSelect_inparameters,DomainCollection) |http://forums.oracle.com/forums/] - WSIF JCA Execute of operation 'doSelect' failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore. [Caused by: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: localhost:1521:XE1 |http://forums.oracle.com/forums/] ; nested exception is: ORABPEL-11622 Could not create/access the TopLink Session. This session is used to connect to the datastore. [Caused by: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: localhost:1521:XE1 |http://forums.oracle.com/forums/] See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. weblogic-ra.xml) and restart the server. Caused by Exception [TOPLINK-4002|http://forums.oracle.com/forums/] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.SQLException: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: localhost:1521:XE1 Error Code: 0. ,detail= Internal Exception: java.sql.SQLException: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: localhost:1521:XE1 Error Code: 0}} ". Please check the error log file for more infromation. A failure is detected in use of fault policy used to recover the activity. Please audit the instance manually or let engine recovery to attempt recovery. Best practice suggests to handle exceptions in fault policy or in the fault handlers in your bpel process. less
com.oracle.bpel.client.BPELFault: faultName: {{[http://schemas.oracle.com/bpel/extension]}remoteFault}
messageType: {{[http://schemas.oracle.com/bpel/extension]}RuntimeFaultMessage}
parts: {{code=0
,summary=file:/D:/oracle/soasuitebasic/bpel/domains/default/tmp/.bpel_Test1BPEL_1.0_7f0af90c7bf1874b5077831987befd2d.tmp/do.wsdl [ do_ptt::doSelect(doSelect_inparameters,DomainCollection) |http://forums.oracle.com/forums/] - WSIF JCA Execute of operation 'doSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
localhost:1521:XE1
; nested exception is:
ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
localhost:1521:XE1
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. weblogic-ra.xml) and restart the server. Caused by Exception [TOPLINK-4002|http://forums.oracle.com/forums/] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
localhost:1521:XE1
Error Code: 0.
,detail=
Internal Exception: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
localhost:1521:XE1
Error Code: 0
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:623)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:437)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:826)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:402)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.expire(BPELInvokeWMP.java:151)
at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:4161)
at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2073)
at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:174)
at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
at com.collaxa.cube.ejb.impl.ActivityManagerBean_lcloe8_ELOImpl.expireActivity(ActivityManagerBean_lcloe8_ELOImpl.java:542)
at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
-----

The fault management framework catches all faults (business and runtime) for an invoke activity only.
For all other activities use the BPEL fault handler.

EDN not available throws runtimeFault - Fault Policy Framework unable to catch it

Hi Team,
I have been working on some error handling scenarios for EDN .
From my observation if BPEL is used to publish the event, BPEL Fault policy cannot catch EDN errors (e.g., EDN unavailable) but BPEL catch activity can catch it.
Steps performed :
1. Create a BPEL to publish the event to EDN.
2.Create fault policy to catch BPEL runtime fault .
3.Go to weblogic console to change EDNdatasource target to get "EDN datasource not available error".
4.Test your BPEL.
My requirement is to retry such faults and invoke human intervention after retry failure using BPEL.
Please let me know how to achieve this

Follow the oracle documentation
- http://docs.oracle.com/cd/E28271_01/dev.1111/e10224/bp_faults.htm#BABIGGIB
*The fault management framework catches all faults (business and runtime) for an invoke activity.*
Hope that helps.
P.S. The fault management framework main purpose is to define a enterprise wide standard policies to handle the faults that will be applied to various/all composite. Hence your specific fault that is specific to a composite should not creep into to fault management framework as this is not the enterprise standard i.e., every composite may have to handle the invalid variable, based on where it occurred and for what variable it occurred.

Non-Recoverable Fault In BPEL

Hi:
I have a BPEL process which is deployed in EM console. I got a error like below saying it as Non-Recoverable error
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><selectionFailure xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"></selectionFailure></bpelFault>.
The problem is this error comes in *"Recent Fault and Rejected Messages"* section everyday between 12AM to 4 AM, even i have deleted the instance which caused the fault but till the error persists. How to stop this?
Regards,
RK

Hi,
Have a look at Arik's blog...
http://ariklalo.wordpress.com/2012/04/25/stop-the-automatic-instances-recovery-on-em/
Cheers,
Vlad

Faults in BPEL when invoked from a Custom built Web Application

Hello there,
I have developed a BPEL flow for a HealthCare demo and it works fine and all is well when it is invoked from the BPEL Console's initiate screen.
I developed a webapplication to invoke the same (using the regular com.collaxa api for invokation of any BPEL process). It invokes the BPEL successfully and I can see the whole Payload in the 'receiveInput' section of the BPEL Flow. But the very First 'Assign' in which i just assign a text string as a default value to an input element faults out stating that the 'to' field is a 'zero node'... The assign stage also shows the payload with all values in it. But it errors out...
here is the payload in the 'receiveInput' stage:
<inputVariable>
<part name="payload" >
<HealthCareWorkFlowProcessRequest>
<enduser_name>pavan</enduser_name>
<enduser_phone_number>08046521345</enduser_phone_number>
<enduser_username>pkvedam</enduser_username>
<enduser_email_id>[email protected]</enduser_email_id>
<problem_desc>cancer</problem_desc>
<prob_relates_to>onchology</prob_relates_to>
<doctor_assigned/>
<doctor_assigned_email_id/>
<proposed_date>13-10-2006</proposed_date>
<proposed_time>09:00</proposed_time>
<proposed_duration>01:00</proposed_duration>
<patient_comments>swelling in the arm pit</patient_comments>
<receptionist_comments/>
<doctor_comments/>
<receptionist_username>employee</receptionist_username>
<receptionist_email_id>[email protected]</receptionist_email_id>
</HealthCareWorkFlowProcessRequest>
</part>
</inputVariable>
Here is the ASSIGN stage errors out (copied to clipboard):
[2006/10/14 10:44:54]
Error in <assign> expression: <to> value is empty at line "46". The XPath expression:
"/child::client:HealthCareWorkFlowProcessRequedst/child::client:receptionist_username"
returns zero node, when applied to document shown below:
<HealthCareWorkFlowProcessRequest>
<enduser_name>pavan</enduser_name>
<enduser_phone_number>08046521345</enduser_phone_number>
<enduser_username>pkvedam</enduser_username>
<enduser_email_id>[email protected]</enduser_email_id>
<problem_desc>cancer</problem_desc>
<prob_relates_to>onchology</prob_relates_to>
<doctor_assigned/>
<doctor_assigned_email_id/>
<proposed_date>13-10-2006</proposed_date>
<proposed_time>09:00</proposed_time>
<proposed_duration>01:00</proposed_duration>
<patient_comments>swelling in the arm pit</patient_comments>
<receptionist_comments/>
<doctor_comments/>
<receptionist_username>employee</receptionist_username>
<receptionist_email_id>[email protected]</receptionist_email_id>
</HealthCareWorkFlowProcessRequest>
<selectionFailure>
<part name="summary" >
<summary>XPath query string returns zero node. According to BPEL4WS spec 1.1 section 14.3, The assign activity <to> part query should not return zero node. Please check the BPEL source at line number "46" and verify the <to> part xpath query. </summary>
</part>
</selectionFailure>

oops... sorry... I had typed it in as there is no way to copy that 'error message' on to the clipboard from the BPEL FLOW depiction.
it must have read 'HealthCareWorkFlowProcessRequest'...
the problem is not with the typo... :(
Am not able to find the root cause... but the flow fails when invoked from my web application...

Fault policy does not work when throwing remoteFault in bpel

Hi
I have a BPEL-proces in which I throw a remoteFault.
In the fault-policy there is a condition for this fault
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-java"/>
</condition>
</faultName>
But the fault-policy does not work if I throw this remoteFault in de bpel. But when I invoke another service (which is shutdown), then I get a remoteFault and for this remoteFault the fault-policy works well.
Any idea why the fault-policy does not work when I throw the remoteFault?
Regards

BPEL fault works only on invocation failures.
Fault management will work based on the remote fault from the remote service, you cannot throw remote fault from bpel and capture that in fault management and process.
The following are the actions that we can take on faults.
1. Human Intervention
2. Rethrow [rethrowFault]
3. Termination [abort]
4. Replay Fault [replayScope]
5. Custom Java Action [javaAction]
6. Retry [retry]
Hope this helps !!!
Thanks,
Vijay

Throwing fault to client

hi all ...first of all i use 10.1.3.1.
1)I have defined a fault in service.xsd:
<complexType name="SubscriberError">
<sequence>
<element minOccurs="1" maxOccurs="1" name="errorCode" type="int"/>
<element minOccurs="1" maxOccurs="1" name="errorDesc" nillable="true" type="string"/>
</sequence>
</complexType>
2)I used this in my service.wsdl:
<message name="SubscriberError">
<part name="fault" type="client:SubscriberError"/>
</message>
3)and finally i changed the port type in service.wsdl as following:
<portType name="denek">
          <operation name="process">
               <input message="client:denekRequestMessage" />
               <output message="client:denekResponseMessage"/>
<fault message="client:SubscriberError" name="SubscriberError"/>
          </operation>
</portType>
Here is the scenario and error :
When i want to throw a fault from BPEL(in reply activity,i set fault message as a response),fault message goes to client as i expected but at every response i see following error in log files . Is it normal to see these in log files and how can i prevent this?
<2007-05-14 14:13:39,079> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": faultName: {{http://xmlns.oracle.com/denek}SubscriberError}
messageType: {{http://xmlns.oracle.com/denek}SubscriberError}
parts: {{fault=oracle.xml.parser.v2.XMLElement@1757d61}}
com.oracle.bpel.client.BPELFault: faultName: {{http://xmlns.oracle.com/denek}SubscriberError}
messageType: {{http://xmlns.oracle.com/denek}SubscriberError}
parts: {{fault=oracle.xml.parser.v2.XMLElement@1757d61}}
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:455)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:278)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:129)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
THKS

thnks Mark
Although i set the audit level to "off", nothing changed. This exception occurs under opmn logs as i mentioned before.
Also i send the fault as mentioned in first post.There is no problem to send fault(i see the fault in client side).
My problem is seeing the following exception in log files.
May be you can help me about the problem in that log files. Can you generate this according to my explanations-in first post.
Also i can send you the case(a sample project to generate this) but i don t know how to attach it.
thks again

Throw customised Faults in BPEL

Similar Messages

Maybe you are looking for