Got it Tammo. Many thanks for the info. So if an instance has failed and completed, I then need to get its failure count if I want to know whether it was completed due to a failure or due to the normal course of action. Thanks.
Yea the term failure was the one which mislead me to the assumption that selectionFailure would throw ActivityFailureEvent. Thanks Dhanush -----Original Message----- From: Tammo van Lessen [mailto:[email protected]] Sent: Thursday, June 03, 2010 7:55 PM To: [email protected] Subject: Re: Failure Events Hi Dhanush, the ActivityFailureEvent is fired when an activity enters a failure and needs manual recovery. Note that there is a difference between Faults and Failures. Faults are expected exceptions, like declared SOAP faults, or the BPEL standard faults like selectionFailure (yes, the term failure is a bit misleading here). Failures on the other side are unexpected exceptions like a connection reset, timeout, etc. In this case the activity cannot complete properly (not even with a fault) so that it enters the failure state and can then be recovered manually via the PM API. HTH, Tammo On 03.06.2010 13:07, Dhanush Gopinath wrote: > Hi, > > > > I just realized that any failure of process execution (for e.g. > selectionFailure) doesn't throw the ActivityFailureEvent event. But > instead it throws the process completion event. As a result of this I am > not able to capture Process Failure. Any idea when the failure event is > thrown? > > > > Thanks & Regards > > Dhanush Gopinath > > > > -- Tammo van Lessen - http://www.taval.de
