Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10518

Connection to remote Artemis broker must not require the presence of a local Artemis broker

    XMLWordPrintable

Details

    • Feature Request
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • None
    • 14.0.0.Final
    • JMS
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes

    Description

      Connections to remote Artemis-based broker (including A-MQ 7) are handled in WildFly by the pooled-connection-factory resource that is in the messaging-activemq subsystem: https://wildscribe.github.io/WildFly/13.0/subsystem/messaging-activemq/server/pooled-connection-factory/index.html

      This pooled-connection-factory resource can be used to connect to the local Artemis server that "owns" it or to a remote Artemis broker.

      However, this pooled-connection-factory always require the presence of a local Artemis server even when it connects only to a remote Artemis broker.
      This use case will become more prevalent as EAP CD is used to connect to A-MQ 7 and will not embed a local Artemis server.

      The presence of a local Artemis server has impact on the memory and CPU footprint of EAP on OpenShift.

      This RFE will improve WildFly and EAP so that a connection with remote Artemis-based broker will no longer require the presence of a local instance of Artemis.

      Attachments

        Issue Links

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              jmesnil1@redhat.com Jeff Mesnil
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: