An null exception occurred when integrating seata

[ulwx]

@Transactional(propagation = Propagation.REQUIRED)
 @GlobalTransactional
 public void updateUseAkDs() {
     TransactionTypeHolder.set(TransactionType.BASE);
     addressDao.updateMdForMaster2(1, "123");
     try {
         addressDao.updateMdForMaster1(2, "abc");
     } catch (Exception ex) {
         LOGGER.debug(ex + "");
     }

 }

An error is reported when integrating seata. When we use sharding-jdbc with seata, a null exception will be reported! The above is my code.

[TeslaCN]

Hi @ulwx
Please provide more information about your question.

[ulwx]

@transactional(propagation = Propagation.REQUIRED)
@GlobalTransactional
public void updateUseAkDs() {
TransactionTypeHolder.set(TransactionType.BASE);
addressDao.updateMdForMaster2(1, "123");
try {
addressDao.updateMdForMaster1(2, "abc");
} catch (Exception ex) {
LOGGER.debug(ex + "");
}

}

@GlobalTransactional is an annotation from seata, indicating that this is a global transaction. When TransactionTypeHolder. set (TransactionType. BASE) is used in a method（using the @ GlobalTransactional annotation）, an error will be reported. The reason is that sharding-jdbc determines in the code that if it is in a global transaction, SeataATShardingSphereTransactionManager#begin() is not executed, finally, in the code ”SeataTransactionHolder. get(). commit()” in the SeataATShardingSphereTransactionManager#commit() method, SeataTransactionHolder. get()=null, resulting in a null exception!

[linghengqian]

• I believe this is essentially a duplicate of SpringCloud+Seata1.5.2+ShardingSphereJDBC5.2.1 SeataATShardingSphereTransactionManager.commit throw null exception #22356 (comment) , and the use of annotations within io.seata:seata-spring-boot-starter should be avoided, including io.seata.spring.annotation.GlobalTransactional.
• I believe this issue involves adjustments to the Spring Boot Starter side of Seata.