ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: [jira] Commented: (ODE-473) If ode crashes while waiting for an response to an synchronous response and while thr has yet not been any timeout , it does not resume on restarting the ode.
Date Tue, 06 Jan 2009 17:50:27 GMT
On Tue, Jan 6, 2009 at 1:42 AM, Rosalin Pattnaik <rosalin.pattnaik@gmail.com
> wrote:

> I tested it with ode 1.2  and the prob remains the same.
> *1st scenario:*
> The bpel invoked the Globalweather service ,waited for response and then
> ode
> timeout.Now the ode crashes.The console message just before the ode crashed
> is as below:

> When restarted the ode, the external webservice was invoked again deu to
> the
> following extension in the invoke activity.
>  <ext:failureHandling xmlns:ext="http://ode.apache.org/activityRecovery">
>                    <ext:faultOnFailure>false</ext:faultOnFailure>
>                    <ext:retryFor>2</ext:retryFor>
>                    <ext:retryDelay>60</ext:retryDelay>
>                </ext:failureHandling>
> and resumed normally.

Right, this is expected.

> *2nd Scenario*:
> When the bpel had invoked the GlobalWeather service and was waiting for
> response but not yet timedout , i shutdown the ode.
> then on restarting it didnt resume the normal flow.The console message just
> before the ode crashed is as below:


The expected sequence of action should be the following,
1) process invokes service
2) server crashes before invoke is successful or timeouts
3) server is restarted
4) when the message exchange times-out (after 120 seconds, I believe) a
scheduled job should mark the exchange as failed and then proceed according
to your activity failure instruction
5) in your case, the invoke should be retried automatically.

Can you test with the latest Ode 1.x branch as requested?   If you're not
getting this expected result then we'll look into it.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message