From 6272d2844e0f2fcacdbf2405a720a20efaa347fe Mon Sep 17 00:00:00 2001
From: dsyer <dsyer@2e8e966d-6415-0410-94b9-dc4e65435d03>
Date: Wed, 16 Sep 2009 16:59:53 +0000
Subject: [PATCH] RESOLVED - issue BATCH-1406: Avoid deadlock with database
 pool and multithreaded step when throttle limit is too high. No need to save
 the step execution in TaskletStep at all.

---
 .../springframework/batch/core/step/tasklet/TaskletStep.java   | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/spring-batch-core/src/main/java/org/springframework/batch/core/step/tasklet/TaskletStep.java b/spring-batch-core/src/main/java/org/springframework/batch/core/step/tasklet/TaskletStep.java
index 4422b8b85..59906bc36 100644
--- a/spring-batch-core/src/main/java/org/springframework/batch/core/step/tasklet/TaskletStep.java
+++ b/spring-batch-core/src/main/java/org/springframework/batch/core/step/tasklet/TaskletStep.java
@@ -383,9 +383,6 @@ public class TaskletStep extends AbstractStep {
 						semaphore.release();
 					}
 					locked = false;
-					if (!committed) {
-						getJobRepository().update(stepExecution);
-					}
 				}
 
 				chunkListener.afterChunk();