Comments (4)
OSS support for Spring Boot 2.7.x has ended so I'm afraid this won't change in Spring Boot 2.x.
If you want to use a caching connection factory with your JMS template but not with your message listener container, you could define either the template or the listener container yourself. The latter is probably the easier of the two:
@Bean
DefaultJmsListenerContainerFactory jmsListenerContainerFactory(
DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) {
DefaultJmsListenerContainerFactory factory = new DefaultJmsListenerContainerFactory();
configurer.configure(factory, ((CachingConnectionFactory)connectionFactory).getTargetConnectionFactory());
return factory;
}
Spring Boot 3.x uses Spring Framework 6.x where the javadoc has been amended and the note softened quite a bit. That said, it still leans towards not using a CachingConnectionFactory
with a listener container.
@jhoeller, what would you recommend here for Boot 3? I doubt that we'd change this in a maintenance release but we could consider unwrapping any caching connection factory in a new minor.
from spring-boot.
Yes, unwrapping is easy. It just breaks reconnecting after broker restart badly.
from spring-boot.
I just reviewed the javadoc change. The change of documentation relating to dynamic scaling might be right. What should be stressed: the CachingConnectionFactory breaks (might be depending on type underlying ConnectionFactory) recovering from broker outage. This is clearly reproducable. In our case it affected the system badly leading to outage of our production system and unessesary downtime affecting our customers.
from spring-boot.
For listener recovery, it is indeed recommendable to configure the message listener containers with the target ConnectionFactory directly, letting them use one Connection per listener container. It's a tradeoff with the number of Connections in the overall application which should be fine in many scenarios, giving full responsibility to each listener container in terms of local recovery.
With a high number of listener containers, I'd consider Connection reuse in the setup but even that does not have to be a global CachingConnectionFactory
, could also be a SingleConnectionFactory
shared among the listener containers - whereas for JmsTemplate usage, there could still be a separate CachingConnectionFactory
for template operations only.
Customizing the DefaultJmsListenerContainerFactory
should do the trick for the time being. For Boot 3.3, we could consider a revised setup strategy by default indeed.
from spring-boot.
Related Issues (20)
- Rework fix for #21992 to avoid polluting Gradle Module Metadata with mavenOptional… variants
- Rework fix for #21992 to avoid polluting Gradle Module Metadata with mavenOptional… variants
- Update Kotlin DSL examples that configure the environment of bootBuildImage to be additive
- Update Kotlin DSL examples that configure the environment of bootBuildImage to be additive
- Make buildSrc's custom tasks consistently abstract
- Make buildSrc's custom tasks consistently abstract
- Make buildSrc's custom tasks consistently abstract
- TransactionalOperator is not configured in Data Neo4j HOT 9
- OtlpMetricsExportAutoConfiguration uses default OTLP metrics url when value comes from Dynamic Properties HOT 2
- Spring Boot 3.X Upgrade: Custom Health Indicator Not Recognized in Actuator Liveness Group HOT 3
- Review auto-configuration that accepts both a URI and separate properties
- @NewSpan/@SpanTag not working on interface methods HOT 3
- PaketoBuilderTests fail due to deprecation warning from the ca-certificates buildpack
- PaketoBuilderTests fail due to deprecation warning from the ca-certificates buildpack
- PaketoBuilderTests fail due to deprecation warning from the ca-certificates buildpack
- Enable eclipse ignoreUnnamedModuleForSplitPackage setting in buildSrc HOT 2
- Not able to use actuator WriteOperation annotation with parameters HOT 3
- Springboot connection database password acquisition error HOT 3
- Springboot connection database password acquisition error HOT 1
- [Feature Request]: Introduce a property to set the server time HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spring-boot.