This content has been marked as final. Show 6 replies
Pls follow this link.1 person found this helpful
Also pls mark the thread with helpful or correct according to forum rules.
Hi,1 person found this helpful
The reason it is "stuck" on running mode is because your process was rolled back and exception was not handheld correctly.
Can you please describe what activity you have in the process and were does the error accrued?
On a selection fault which is not handled out of seedeed faults, it is going to catchall block. In catch all block, I am having an assign for AIAAsyncErrorHandlingBpelProcess variable and invoke to AIAASyncErrorHandlingBpelProcess followed by throw which throws the AIAAsync Input variable. So at runtime, the selection fault is leading the process to catchall and the isntance shows as faulted since we have throw but the process state shows Running and goes to manual recovery. Can you please suggest on this.
Throw activity in your case (that throws the AIAAsync Input variable)will not terminate the process.1 person found this helpful
You can just use Termintae.
Why you are using another throw?
As per Oracle standards of Fault Handling, there should be a throw activity in each of the catch blocks so that on any faults either catch or catchall, the instance is shown as faulted. Correct me if I am wrong. We have used throw in catch(binding fault, remote fault) and catchall(aiaasyncerrorprocess). If we terminate the process then does it show as faulted?
If the only reason is to show an exception in the EM then you can use the Terminate activity.
Thorw activity many times can casue other beheviour to your process.