-
Story
-
Resolution: Done
-
Critical
-
None
-
None
The currently implemented solution (https://github.com/quarkiverse/quarkus-pooled-jms) only works with quarkus-artemis-jms (which is a community client).
For the future, it looks like AMQ team is not willing to support pooling on their side, even thought client provides pooling for spring-boot.
We productize quarkus-pooled-jms and use quarkus-artemis-jms
We need to do some change in Quarkus core for the next release to make it more generic.
For example it should be possible to use pooling with IBM MQ
Provide full support for the connection pooling.
Updates:
- Quarkus >= 2.16.3.Final: quarkus-pooled-jms 1.1.0 works with quarkus-artemis 2.1.0
- Breaking configuration changes: quarkus.pooled-jms.xa.enabled=true changes to quarkus.pooled-jms.transaction=xa
- Quarkus 3.0.0.Final: quarkus-pooled-jms 2.0.1 works with quarkus-artemis 3.0.0
- The same configuration changes like above
- quarkus-qpid-jms 2.1.0 is supported. https://github.com/amqphub/quarkus-qpid-jms/issues/22 is closed.
- It need to quarkus.qpid-jms.wrap=true
- There is IBM MQ client support from the community
- is related to
-
CEQ-833 JMS components connection pooling (with artemis, tech-preview)
- Closed
- links to
-
RHEA-2023:123625 Red Hat Build of Apache Camel for Quarkus 3.2.0 release (RHBQ 3.2.6.SP1)