Any ways to rollback transaction other than throwing exception?

[tadaya]

Hello,

In order to rollback the transaction used by each job execution, throwing exception in processor or writer is the only way?
By throwing an exception, the execution will be marked as failure. But in my case, I'd like to successfully run job with intentional rollback.

Usecase is like this:
My batch process is regular style - read from DB, process it, then write to DB.
I want to run the batch as if it run successfully but without persisting the result into database. The reason of not persisting data is testing the batch job in production with real data.
By running job with no persisting, we obtain all logging, statistics information about the batch job without affecting production data. We observe those collected information, then once everything is ok, we flip the switch and start persisting data.

So, rolling back transaction at the end of the execution is the pretty much best way for this scenario because I can even test the database constraints by writing the object in writer(then rollback later).

I tried to retrieve the transaction used by trsnsactionTemplate in TaskletStep, but couldn't get it in writer or chunklistener classes.

It would be nice if I can get the transaction(TransactionStatus) in listener and could able to call the setRollbackOnly().

[litius]

The reason of not persisting data is testing the batch job in production with real data

Can you run it against the production data from within a transactional integration test ( @TransactionConfiguration / @Transactional ) where 'defaultRollback' is already set to true?

This way you won't be changing your jobs before running them in production.

/Anatoly

[tadaya]

ah, i see. I got what you meant, Anatoly, Thanks.

We deploy app to the production env & dryrun the batch and collect the statistics.
We keep the app running in dryrun for a couple of days/weeks to observe the statistics.
When we think everything is ok, we change one of the value in the app, then start persisting data.


So, I wrote a delegator class which wraps PlatformTransactionManager and controls commit/rollback.

impl

public class RollbackTransactionManager implements PlatformTransactionManager {

    private PlatformTransactionManager transactionManager;
    private boolean doRollback;

    public void commit(TransactionStatus status) throws TransactionException {
        if (doRollback) {
            transactionManager.rollback(status);
        } else {
            transactionManager.commit(status);
        }
    }
     ......
}

job config file

  <!-- provides a real txmanager to job repository -->
  <batch:job-repository id="jobRepository" transaction-manager="transactionManager"/>

  <batch:job id="job">
    <batch:step id="step">
      <!-- provides a wrapped txmanager -->
      <batch:tasklet transaction-manager="rollbackAwareTxManager">
        <batch:chunk reader="sampleReader" writer="sampleWriter"/>
      </batch:tasklet>
    </batch:step>
  </batch:job>

  <bean id="rollbackAwareTxManager" class="com.foobar.RollbackTransactionManager">
    <property name="transactionManager" ref="transactionManager" />
  </bean>