Uploaded image for project: 'Red Hat Build of Apache Camel for Quarkus'
  1. Red Hat Build of Apache Camel for Quarkus
  2. CEQ-4878

JMS components connection pooling (generic client, full support)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • 3.2.0.GA
    • None
    • Camel Quarkus
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 0

      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

            zfeng@redhat.com Zheng Feng
            ibek1@redhat.com Ivo Bek
            Tomas Turek Tomas Turek
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: