Closed graben closed 2 days ago
Thanks for the sample, see also #39816.
is causing issue with Narayana
What does that mean? ~How do I reproduce the problem with the sample you've shared and what is the problem. I've tried to run the application and didn't see a problem except an exception on shutdown that can happen unfortunately with ActiveMQ.~ Nevermind, I see now that building Narayana is required.
For those affected by the issue, you can add the following to your configuration to create a DefaultJmsListenerContainerFactory
that doesn't do the unwrapping:
@Bean
DefaultJmsListenerContainerFactory jmsListenerContainerFactory(
DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) {
DefaultJmsListenerContainerFactory factory = new DefaultJmsListenerContainerFactory();
configurer.configure(factory, connectionFactory);
return factory;
}
@graben I've added the above in DemoApplication
and that restored the behavior for now.
@snicoll: Thanks for the workaround. Works for me, too! ;-)
The unwrapping code introduced with commit into
JmsAnnotationDrivenConfiguration
is causing issue with Narayana integration if using pooled ConnectionFactory because it unwraps the integration "magic" away.Reproduce with attached demo. Btw. Narayana integration from https://github.com/snowdrop/narayana-spring-boot needs to be rebuilt as SNAPSHOT because latest 3.3.0 version is not build compatible with Spring Boot 3.4.0. (snowdrop/narayana-spring-boot#172)
demo.zip
FYI @snicoll