You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Sean Ahn (JIRA)" <ji...@apache.org> on 2009/10/14 23:04:31 UTC
[jira] Created: (ODE-680) Do not send back the response right away
when a transaction fails
Do not send back the response right away when a transaction fails
-----------------------------------------------------------------
Key: ODE-680
URL: https://issues.apache.org/jira/browse/ODE-680
Project: ODE
Issue Type: Improvement
Reporter: Sean Ahn
Priority: Minor
ODE engine currently reschedules a job if the job fails in most cases. If a database transaction fails due to a deadlock, in many cases the job success on the second try. However, we're sending back the response right away after the first try.
1. Do not send back the response if the transaction is being rolled back.
2. Send back a failure response on the mex time out. If the mex time out value is larger than the client time out, the client will get a time out on the response. But, during development, people can get a better response by controlling the mex time out value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-680) Do not send back the response right away
when a transaction fails
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn resolved ODE-680.
--------------------------
Resolution: Fixed
The behavior is now as followings:
1. A request comes in to the engine. A job is scheduled with a transaction.
2. For any reason, if the transaction fails, a response is not generated any longer.
3. The engine schedules the job later. At the time, the transaction succeeds. The response is generated with the right message.
4. If multiple times of rescheduling the job fails and when the mex times out, the old plain 'mex time out' error is sent back to the client.
r825703 | seanahn | 2009-10-15 16:44:34 -0700 (Thu, 15 Oct 2009) | 1 line
Changed paths:
M /ode/branches/APACHE_ODE_1.X/bpel-runtime/src/main/java/org/apache/ode/bpel/engine/MyRoleMessageExchangeImpl.java
A /ode/branches/APACHE_ODE_1.X/bpel-runtime/src/test/java/org/apache/ode/bpel/engine/MyRoleMessageExchangeImplTest.java
> Do not send back the response right away when a transaction fails
> -----------------------------------------------------------------
>
> Key: ODE-680
> URL: https://issues.apache.org/jira/browse/ODE-680
> Project: ODE
> Issue Type: Improvement
> Reporter: Sean Ahn
> Assignee: Sean Ahn
> Priority: Minor
>
> ODE engine currently reschedules a job if the job fails. If a database transaction fails due to a deadlock, in many cases, the job succeeds on the second try. However, we're sending back the response right away after the first try.
> 1. Do not send back the response if the transaction is being rolled back.
> 2. Send back a failure response on the mex time out. If the mex time out value is larger than the client time out, the client will get a time out on the response. But, during development, people can get a better response by controlling the mex time out value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-680) Do not send back the response right away
when a transaction fails
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-680:
-------------------------
Description:
ODE engine currently reschedules a job if the job fails. If a database transaction fails due to a deadlock, in many cases, the job succeeds on the second try. However, we're sending back the response right away after the first try.
1. Do not send back the response if the transaction is being rolled back.
2. Send back a failure response on the mex time out. If the mex time out value is larger than the client time out, the client will get a time out on the response. But, during development, people can get a better response by controlling the mex time out value.
was:
ODE engine currently reschedules a job if the job fails in most cases. If a database transaction fails due to a deadlock, in many cases the job success on the second try. However, we're sending back the response right away after the first try.
1. Do not send back the response if the transaction is being rolled back.
2. Send back a failure response on the mex time out. If the mex time out value is larger than the client time out, the client will get a time out on the response. But, during development, people can get a better response by controlling the mex time out value.
> Do not send back the response right away when a transaction fails
> -----------------------------------------------------------------
>
> Key: ODE-680
> URL: https://issues.apache.org/jira/browse/ODE-680
> Project: ODE
> Issue Type: Improvement
> Reporter: Sean Ahn
> Assignee: Sean Ahn
> Priority: Minor
>
> ODE engine currently reschedules a job if the job fails. If a database transaction fails due to a deadlock, in many cases, the job succeeds on the second try. However, we're sending back the response right away after the first try.
> 1. Do not send back the response if the transaction is being rolled back.
> 2. Send back a failure response on the mex time out. If the mex time out value is larger than the client time out, the client will get a time out on the response. But, during development, people can get a better response by controlling the mex time out value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ODE-680) Do not send back the response right away
when a transaction fails
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn reassigned ODE-680:
----------------------------
Assignee: Sean Ahn
> Do not send back the response right away when a transaction fails
> -----------------------------------------------------------------
>
> Key: ODE-680
> URL: https://issues.apache.org/jira/browse/ODE-680
> Project: ODE
> Issue Type: Improvement
> Reporter: Sean Ahn
> Assignee: Sean Ahn
> Priority: Minor
>
> ODE engine currently reschedules a job if the job fails in most cases. If a database transaction fails due to a deadlock, in many cases the job success on the second try. However, we're sending back the response right away after the first try.
> 1. Do not send back the response if the transaction is being rolled back.
> 2. Send back a failure response on the mex time out. If the mex time out value is larger than the client time out, the client will get a time out on the response. But, during development, people can get a better response by controlling the mex time out value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.