Common Reasons Why Spring @Transactional May Not Work

0x01: Database does not support transactions – Transactions only work with databases that support them; for example, using MySQL with the MyISAM engine disables transactions, while switching to InnoDB enables them.

0x02: Service class not managed by Spring – Spring’s transaction management relies on AOP; if the service class is not a Spring bean, the @Transactional annotation has no effect.

0x03: Internal method calls – Calling a transactional method from another method within the same class using this.xxx() bypasses the proxy, so the transaction is not applied. A common fix is to split the class so that the call goes through a Spring‑managed bean.

Example implementation:

@Service
public class OrderServiceImpl implements OrderService {
    public void update(Order order) {
        updateOrder(order);
    }

    @Transactional
    public void updateOrder(Order order) {
        // update order
    }
}

0x04: Default rollback behavior – Spring rolls back only on unchecked exceptions (RuntimeException). Checked exceptions such as IOException are not rolled back unless you specify rollbackFor = Exception.class.

0x05: Transactional annotation works only on public methods – Applying @Transactional to protected, private, or package‑private methods is ignored without any error.

0x06: Data source lacks a transaction manager – Without a configured PlatformTransactionManager, all transaction annotations are ineffective. Define a bean such as:

@Bean
public PlatformTransactionManager txManager(DataSource dataSource) {
    return new DataSourceTransactionManager(dataSource);
}

In summary, to ensure Spring transactions function correctly, use a transaction‑supporting database engine, make service classes Spring beans, avoid internal self‑calls, annotate only public methods, configure rollback for checked exceptions when needed, and provide a proper transaction manager bean.