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.
This commit is contained in:
@@ -383,9 +383,6 @@ public class TaskletStep extends AbstractStep {
|
||||
semaphore.release();
|
||||
}
|
||||
locked = false;
|
||||
if (!committed) {
|
||||
getJobRepository().update(stepExecution);
|
||||
}
|
||||
}
|
||||
|
||||
chunkListener.afterChunk();
|
||||
|
||||
Reference in New Issue
Block a user