[
https://issues.apache.org/jira/browse/ODE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Ahn resolved ODE-681.
--------------------------
Resolution: Fixed
The SimpleScheduler.execTransaction() now tries the transaction multiple times
for configured number of times when:
1. the transaction fails
2. the transaction succeeds but committing of the transaction fails
r826142 | seanahn | 2009-10-16 17:24:56 -0700 (Fri, 16 Oct 2009) | 1 line
Changed paths:
M /ode/branches/APACHE_ODE_1.X/Rakefile
M
/ode/branches/APACHE_ODE_1.X/scheduler-simple/src/main/java/org/apache/ode/scheduler/simple/SimpleScheduler.java
M
/ode/branches/APACHE_ODE_1.X/scheduler-simple/src/test/java/org/apache/ode/scheduler/simple/DelegateSupport.java
A
/ode/branches/APACHE_ODE_1.X/scheduler-simple/src/test/java/org/apache/ode/scheduler/simple/GeronimoDelegateSupport.java
M
/ode/branches/APACHE_ODE_1.X/scheduler-simple/src/test/java/org/apache/ode/scheduler/simple/RetriesTest.java
> Implement immediate transaction retries in addition to the presistent retries
> -----------------------------------------------------------------------------
>
> Key: ODE-681
> URL: https://issues.apache.org/jira/browse/ODE-681
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Runtime
> Reporter: Sean Ahn
> Assignee: Sean Ahn
>
> Currently, the ode engine re-schedules a job into the ODE_JOB table when the
> job fails. The job will be picked up later by the job scheduler on the same
> node. For 2 reasons, we want to pre-pend an immediate transaction retry logic
> before the persistent retries.
> 1. The current way of scheduling a job involves deleting of the job and
> inserting/selecting of a new job for a retry. If the system is under heavy
> load, and if the failure was due to deadlocks from database overload, you do
> not want to put on even more load.
> 2. The interval between retries could be pretty long. Cases like database
> deadlocks can be resolved by re-trying the same transaction in a relatively
> short time.
> Repeat the same transaction by configurable number of tries with a
> configuration interval. If all tries still fail, then schedule the job for
> persistent retries.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
