[
https://issues.apache.org/jira/browse/ODE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexis Midon resolved ODE-551.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0
1.3.1
Fixed in 1.X and trunk.
The check job is now scheduled based on the mex timeout of the invoked endpoint.
To make sure the check job does not get executed while the service invocation
is still waiting for a response. the date is computed as follow:
now + mex.timeout * 1.5
> Timeout for Check Job should be equal to mex timeout
> ----------------------------------------------------
>
> Key: ODE-551
> URL: https://issues.apache.org/jira/browse/ODE-551
> Project: ODE
> Issue Type: Bug
> Reporter: Alexis Midon
> Assignee: Alexis Midon
> Fix For: 1.3.1, 2.0
>
>
> In org.apache.ode.bpel.engine.BpelRuntimeContextImpl#scheduleInvokeCheck, a
> 3mn timeout is hardcoded. This could cause problem if the mex timeout is
> greater than 3mn. Actually the check job will be executed and the mex failed.
> So the correct timeout should be equal or slightly greater than the mex
> timout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
