Vlastimil K

A workaround would be manual transaction manager initialization. Over the time, I was trying to figure out the repro steps, but I was not successful. It just happens only with...

In our case, the issue was caused by a custom autoconfiguration: ``` @ConditionalOnBean(PlatformTransactionManager.class) @AutoConfiguration(after = TransactionAutoConfiguration.class) public class CustomAutoConfiguration { ``` We had to add `@AutoConfigureOrder(Ordered.LOWEST_PRECEDENCE)` to this class, and...