Reinstate support for pooled-jms as it is now JMS 3.0 compatible

Closes gh-30865
This commit is contained in:
Andy Wilkinson
2022-05-04 17:31:14 +01:00
parent 24dcdbb4a1
commit 1ee079c265
8 changed files with 305 additions and 0 deletions

View File

@@ -43,6 +43,19 @@ By default, a `CachingConnectionFactory` wraps the native `ConnectionFactory` wi
session-cache-size: 5
----
If you'd rather use native pooling, you can do so by adding a dependency on `org.messaginghub:pooled-jms` and configuring the `JmsPoolConnectionFactory` accordingly, as shown in the following example:
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
----
spring:
artemis:
pool:
enabled: true
max-connections: 50
----
See {spring-boot-autoconfigure-module-code}/jms/artemis/ArtemisProperties.java[`ArtemisProperties`] for more supported options.
No JNDI lookup is involved, and destinations are resolved against their names, using either the `name` attribute in the Artemis configuration or the names provided through configuration.