Suppose I use 2 threads in a transaction to speed up processing. If the userDao.addOrg() method throws a RuntimeException, the transaction will not be rolled back and the error will not be caught. What should I do? Is that right?
ExecutorService executorService = Executors.newCachedThreadPool();
@Transactional(rollbackFor=Throwable.class)
public void add(){
CountDownLatch cdl = new CountDownLatch(2);
executorService.submit(new Runnable() {
public void run() {
userDao.addOrg(); //抛出RuntimeException异常
cdl.countDown();
}
});
executorService.submit(new Runnable() {
public void run() {
userDao.addSystem();
cdl.countDown();
}
});
cdl.wait(10,TimeUnit.SECONDS);
}
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
@Transactional can only control single-threaded transactions, so child threads are not controlled by transactions on the add method. You can start a new transaction on the method called by the child thread and roll back.
Enable child threads to call transaction-controlled methods:
Note that @Transactional is implemented through proxy, so addMethod must be placed in the new class AddOperation and cannot be placed in the class where the add method is located.