Did you read our documentation about Activity Failure and Recovery<http://ode.apache.org/bpel-extensions.html#BPELExtensions-ActivityFailureandRecovery>?
On 9/21/07, Jens Goldhammer <[EMAIL PROTECTED]> wrote: > > > I have the same problem as described! Does anybody know the solution? Are > internal exception are handled by these faultHandlers? > > Regards, > Jens > > > > Andreas Holubek wrote: > > > > Hi, > > > > Maybe this is a simple question, but this time I see no solution... I > have > > a > > process which tries to invoke a simple web service. At execution time of > > the > > process the web service is down. > > > > Normally I expect to catch the exception with some sort of fault > handler: > > > > <scope name="__invoke_scope"> > > <faultHandlers> > > <catchAll> > > <empty name="_Connection_refused_"/> > > </catchAll> > > </faultHandlers> > > > > <invoke name="__invoke" > > inputVariable="addVar" > > operation="addNumbers" > > outputVariable="addVarResponse" > > partnerLink="addNumbersPartnerLink" > > portType="test:AddNumbersPartnerLinkType"/> > > </scope> > > > > I use pxe-standalone-distro-1.0.164 and have full logging enabled. I see > > the > > connection refused exception within the log. But it seems that the empty > > activity is not executed. The pxe hangs and after a while I get the soap > > message: "Timeout waiting for response; operation may complete in the > > future." Maybe something is wrong in the bpel code? > > > > Thanks for your help, > > Andreas > > > > > > > > -- > View this message in context: > http://www.nabble.com/Problem-with-fault-handler-tf2692852.html#a12825366 > Sent from the Apache Ode User mailing list archive at Nabble.com. > >
