Hi Jitendra, just remove the faulthandler and add instead the following block:
<ext:failureHandling> <ext:retryFor>0</ext:retryFor> <ext:retryDelay>0</ext:retryDelay> </ext:failureHandling> as described in http://ode.apache.org/extensions/activity-failure-and-recovery.html. The instance will then remain in ACTIVE state and waits for the recovery. Also see https://github.com/apache/ode/blob/master/bpel-runtime/src/test/resources/recovery/failure-to-recovery.bpel for an example BPEL file. I'm currently developing a new console for ODE which also supports activity recovery. It is pre-alpha but if you want I can share it with you, also hoping for a little feedback :) Best, Tammo On Mon, Jan 12, 2015 at 12:30 PM, Kharche, Jitendra < [email protected]> wrote: > Hi, > > I would like to develop a process in which it should be possible to retry > an invoke activity upon external fault. > The invoke activity invokes an external service that may throw an > exception. > When an exception occurs I want to retry the activity (manual or auto). > > In my earlier process I did following steps: > > 1. Put a CatchAll FaultHandler at process level to catch all the > external faults > > 2. Send a notification to administrator. > But this takes the process instance into COMPLETED state and cannot be > retried. In the new process, instead of this I want the process instance to > remain in ACTIVE state at the faulted activity so that I can retry it. > > I would like to know what care I should take to achieve this during > process implementation. > > > Regards, > Jitendra > -- Tammo van Lessen - http://www.taval.de
