You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexey Ousov (JIRA)" <ji...@apache.org> on 2008/04/29 08:33:56 UTC
[jira] Created: (ODE-276) Configurable timeout for MEX?
Configurable timeout for MEX?
-----------------------------
Key: ODE-276
URL: https://issues.apache.org/jira/browse/ODE-276
Project: ODE
Issue Type: Improvement
Components: BPEL Runtime
Reporter: Alexey Ousov
Priority: Minor
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!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-276) Configurable timeout for MEX?
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou updated ODE-276:
------------------------------
Fix Version/s: 1.2
> Configurable timeout for MEX?
> -----------------------------
>
> Key: ODE-276
> URL: https://issues.apache.org/jira/browse/ODE-276
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Reporter: Alexey Ousov
> Priority: Minor
> Fix For: 1.2
>
>
> 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!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-276) Configurable timeout for MEX?
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-276.
-------------------------------
Resolution: Fixed
Assignee: Matthieu Riou
> Configurable timeout for MEX?
> -----------------------------
>
> Key: ODE-276
> URL: https://issues.apache.org/jira/browse/ODE-276
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Reporter: Alexey Ousov
> Assignee: Matthieu Riou
> Priority: Minor
> Fix For: 1.2
>
>
> 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!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-276) Configurable timeout for MEX?
Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592980#action_12592980 ]
Mateusz Nowakowski commented on ODE-276:
----------------------------------------
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.
> Configurable timeout for MEX?
> -----------------------------
>
> Key: ODE-276
> URL: https://issues.apache.org/jira/browse/ODE-276
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Reporter: Alexey Ousov
> Priority: Minor
>
> 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!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.