commit-interval in Spring batch and dealing with rollbacks

java transactions spring-batch commit chunks
balteo picture balteo · Jul 11, 2012 · Viewed 17.2k times · Source

My question relates to Spring batch and transactions.

Say I've chosen a commit-interval of 50 for one of my steps.

Also suppose I have 1000 records in all and amongst those records one will cause the itemWriter to fail thereby causing a rollback of the entire chunk (50 records in my example).

What are the stategies to make sure that the 49 valid records are written to database after the job has completed (and ignored the problematic chunk)?

Answer

balteo picture balteo · Jul 11, 2012

After some researching, I came up with the following:

If an item writer fails to commit a chunk (here 50 items) thereby causing a rollback, Spring Batch will rerun each item of the problematic chunk individually with one commit/transaction for each item.

Therefore, all 49 items will be present in database except the one item that caused Spring Batch to roll back the chunk.

Related questions

Spring TransactionManager - commit does not work

I am trying to create Spring-based solution for running batch of SQL queries on MySQL 5.5 server. By "query" I mean any SQL statement that compiles, so the SQL batch job can contain for example several CREATE TABLE, DELETE and then …

Read More
Where does the @Transactional annotation belong?

Should you place the @Transactional in the DAO classes and/or their methods or is it better to annotate the Service classes which are calling using the DAO objects? Or does it make sense to annotate both "layers"?

Read More
Transaction marked as rollback only: How do I find the cause

I am having issues with committing a transaction within my @Transactional method: methodA() { methodB() } @Transactional methodB() { ... em.persist(); ... em.flush(); log("OK"); } When I call methodB() from methodA(), the method passes successfuly and I can see "OK" in my logs. …

Read More