Issue Details (XML | Word | Printable)

Key: ODE-276
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Matthieu Riou
Reporter: Alexey Ousov
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ODE

Configurable timeout for MEX?

Created: 29/Apr/08 06:32 AM   Updated: 06/Jun/08 05:51 PM
Return to search
Component/s: BPEL Runtime
Affects Version/s: None
Fix Version/s: 1.2

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Incorporates
 

Resolution Date: 06/Jun/08 05:51 PM


 Description  « Hide
I would like to have configurable (with ode-axis2.properties) option to manage MEX timeouts, instead of currently used:
public static final int TIMEOUT = 2 * 60 * 1000;

For example while profiling some BPEL process, this timeout is not enough, and process exits with:
13:23:24,156 ERROR ODEService.onAxisMessageExchange(148) : Timeout or execution error when waiting for response to MEX {MyRoleMex#hqejbhcnphr38ev26lux7j [Client hqejbhcnphr38ev26lux7i] calling {http://www.comped.it/registerUser}registerUser.registerUser(...)} java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@62812d timed out when waiting for a response!


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mateusz Nowakowski added a comment - 29/Apr/08 08:52 AM
I think I have some other requirements.

This issue has probably something in common with ODE-263

It would be nice if this timeout has something is common with particular MEX.

So I would add some class to ode-xxx.properties which would determine timeout value for particular MEX instead of a static value.

Matthieu Riou added a comment - 06/Jun/08 05:51 PM
Fixed by ODE-295