[
https://issues.apache.org/jira/browse/ODE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafal Rusin resolved ODE-473.
-----------------------------
Resolution: Fixed
Fix Version/s: 1.3.4
It's already fixed
> 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.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ODE-473
> URL: https://issues.apache.org/jira/browse/ODE-473
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Rosalin Pattnaik
> Priority: Critical
> Fix For: 1.3.4
>
>
> If we have bpel extension for retry on timeout with an invoke action , but
> the ode crashes before the timeout has occured .And thus there is neither a
> timeout exception nor has it received the response which might have been lost
> in the time it was down .When the ode restarts which of the following shd
> occur:
> * The ode resumes from the invoke state ,waits for the response ,
> timesout and retries, get the response and proceed normally.
> * The process is not resumed.
> In my case the process is not resumed in case timeout exception has not
> occured , but in case the timeout has occured and then the ode crashes then
> it retries gets the response and then completes succesfully.
> [N.B It resumed in case there was an entry into the ode_activity_recovery
> table , or else it didnt]
> Please find the BPEL and external service used as attachment with the query
> posted at ode user forum :
> http://www.nabble.com/If-ode-crashes-while-waiting-for-an-response-to-an-synchronous-response-and-while-thr-has-yet-not-been-any-timeout-%2C-Does-it-on-restarting-resume-the-process-and-the-timesout-the-invoke-activity--td21248664.html
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
