This content has been marked as final. Show 4 replies
Sharmistha,1 person found this helpful
Please note that -
Fault policies are applicable to parallel routing rules only. For sequential routing rules, the fault goes back to the caller. It is the responsibility of the caller to handle the fault. If the caller is an adapter, then you can define rejection handlers on the inbound adapter to take care of the messages that error out (that is, the rejected messages). For more information about rejection handlers, see the Oracle Fusion Middleware User's Guide for Technology Adapters.If you are using parallel routing rule then make sure that the fault being raised has mediatorErrorCode as "TYPE_FATAL_MESH"
Thanks for the reply.
As per the oracle document "TYPE_FATAL_MESH: Contains fatal errors from the Service Infrastructure such as Invoke service not available." , that's why when I shut down down the service , the fault policy file should work.
After changing the routing rule from sequential to parallel, i am facing a different kind of issue. All the faulted instance become "Recoverable" instead of terminated.
Even i changed my code in fault-policies.xml as :
<test>$fault.faultCode = "ORAMED-03303")</test>
It is not working :(
Fault Message :
System Fault :
ORAMED-03303:[Unexpected exception in case execution]Unexpected exception in request response operation "sayHello" on reference "NamePrintService". Possible Fix:Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services. Cause:javax.xml.ws.WebServiceException: Could not determine wsdl ports.
This fault can be recovered.To recover, select this fault in the table and choose a recovery action from the recovery panel.
Thanks in adv,
Even I am facing the same issue.
It is going to recoverable state instead of getting terminated. In my case i am calling a java class and then terminating it.
Please update the thread if you find the solution.
There was an issue with the java class i was invoking through fault policy.
I corrected it and now it is terminating the instance.
Edited by: Hg on May 9, 2013 12:15 AM