Circular dependency on TransactionManager Bean in Spring Batch

The issue you’re encountering is related to Spring's @Primary annotation and bean resolution.

How the Circular Dependency Arises

• Default Wiring by Type: By naming the method transactionManager, Spring might infer that you are providing a default TransactionManager for the application, and it could lead to an implicit circular dependency if other beans depend on TransactionManager.

• Spring's Bean Resolution: Spring resolves beans by both name and type. Since the name of your bean matches the TransactionManager type, Spring might attempt to inject this bean in other places, causing a circular dependency.

Suggested Solutions

1. Use @Qualifier for Explicit Wiring

If you have multiple TransactionManager beans, you can resolve ambiguity by explicitly specifying which one to use in each case. You can use @Qualifier to instruct Spring where and which TransactionManager to use:

@Bean
@Primary
public JtaTransactionManager jtaTransactionManager(UserTransaction userTransaction, 
                                                   @Qualifier("customTransactionManager") TransactionManager transactionManager) {
    JtaTransactionManager jtaTransactionManager = new JtaTransactionManager(userTransaction, transactionManager);
    jtaTransactionManager.setAllowCustomIsolationLevels(true);
    return jtaTransactionManager;
}

2. Lazy Initialization

Another approach is to use @Lazy on your TransactionManager bean. Spring will delay the initialization of the JtaTransactionManager bean until it’s explicitly needed, which may help break the circular dependency

@Bean
@Primary
@Lazy
public JtaTransactionManager transactionManager(UserTransaction userTransaction, 
                                                TransactionManager transactionManager) {
    JtaTransactionManager jtaTransactionManager = new JtaTransactionManager(userTransaction, transactionManager);
    jtaTransactionManager.setAllowCustomIsolationLevels(true);
    return jtaTransactionManager;
}

By using @Qualifier, @Lazy, you should be able to avoid circular dependencies.

I have tried your suggestions and here is that I can say.

@Qualifier and @Lazy doesn't work. @Bean(name = "transactionManager2") is a right solution but with Andrey answer I choice this :

@Bean
@Primary
public JtaTransactionManager jtaTransactionManager(UserTransaction userTransaction,
                                                   TransactionManager transactionManager) {
    JtaTransactionManager jtaTransactionManager = new JtaTransactionManager();
    jtaTransactionManager.setUserTransaction(userTransaction);
    jtaTransactionManager.setTransactionManager(transactionManager);
    jtaTransactionManager.setAllowCustomIsolationLevels(true);
    return jtaTransactionManager;
}

Thanks for your help.