How to use Java @Transactional to specify rollback conditions

Exception classification

• ##Checked exceptions: Exceptions under Exception except RuntimeException

• Unchecked exceptions: RuntimeException and its subclasses and errors (Error)

@Transactional annotation attribute details

AttributeTypeDescriptionvalueStringOptional qualification Descriptor, specifying the transaction manager usedpropagationenum: PropagationOptional transaction propagation behavior settingsisolationenum: IsolationOptional transaction isolation level settingreadOnlybooleanRead-write or read-only transaction, default read-writetimeoutint (in seconds granularity)Transaction timeout setting rollbackForArray of Class objects, must inherit from ThrowableArray of exception classes that cause transaction rollbackrollbackForClassNameArray of class names, must inherit from ThrowableArray of exception class names that cause transaction rollbacknoRollbackForClass object array, must inherit from ThrowableException class array that will not cause transaction rollbacknoRollbackForClassNameClass name array, must Inherited from ThrowableNumber of exception class names that will not cause transaction rollback@Transactional

When using the @Transaction annotation, Ali The Baba code specification plug-in will remind you that you need to specify rollbackFor to display the rollback

By default, the Spring framework only throws a run in

when using @Transaction to process transactions. The transaction will be rolled back only when exceptions and unchecked exceptions occur. That is, when an instance of RuntimeException or its subclass is thrown, Checked exceptions thrown from the transaction method will not be marked for transaction rollback.

• Let the checked exception rollback: add

  @Transactional(rollbackOn=Exception.class)

## before the entire method #Let unchecked exceptions not be rolled back:
• @Transactional(dontRollbackOn=RunTimeException.class)
  ##Methods that do not require transaction management (query only):
@Transactional(propagation=Propagation.NOT_SUPPORTED)
Note

:

If the exception is try-catch , the transaction will not be rolled back. If you want the transaction to be rolled back, you must throw

try｛｝catchthrow Exception｝
• .
  The Spring team recommends using the @Transactional annotation on specific classes (or class methods), rather than on any interface that the class wants to implement. You can also use the @Transactional annotation on the interface, but in this case it will only take effect if you need to set up an interface-based proxy

• @Transactional annotation identifies the method. It is recommended that the processing process be as simple as possible. Especially for transaction methods with locks, it is best not to put them in transactions if they can be avoided. Regular database query operations can be placed in front of the transaction, and operations such as addition, deletion, and modification can be placed in the transaction

• code

@Slf4j
@Service
public class MemberService {

    @Autowired
    private MemberMapper memberMapper;

    @Transactional
    public Integer insert(MemberEntity memberEntity) {
        Integer insertResult = 0;
        try {
            insertResult = memberMapper.save(memberEntity);
            log.info("insertResult:{}", insertResult);
            int result = 1 / memberEntity.getAge();
        } catch (Exception e) {
            log.error("errorMsg:{}", e.getMessage());
            //回滚
            TransactionAspectSupport.currentTransactionStatus().setRollbackOnly();
        }
        return insertResult;
    }
}

as shown in the red code , if you don't write it, the transaction will not be rolled back. Because the transaction is caught by catch, the transaction can only be rolled back manually.

The above is the detailed content of How to use Java @Transactional to specify rollback conditions. For more information, please follow other related articles on the PHP Chinese website!