3 Replies Latest reply on Apr 14, 2017 9:36 PM by jbertram

    Wildly 10 - Connection to an external JMS Broker

    vincent.sourin

      Hello,

       

       

      I have an use case where I have to produce a JMS message to an external broker (actually a standalone Artemis activeMQ) from an EJB.

       

      I'm a little lost and I'd like to know what is the correct/best way to do it.

       

      1/ Should I use a JMS Bridge between Wildfly embedded artemis broker and the external one (as described here : https://docs.jboss.org/author/display/WFLY10/Messaging+configuration) ?

       

      2/ Or Should I use a pooled-connection-factory (as described here : https://docs.jboss.org/author/display/WFLY10/Connect+a+pooled-connection-factory+to+a+Remote+Artemis+Server).

       

      Thanks in advance for your advices.

       

      Vincent.

        • 1. Re: Wildly 10 - Connection to an external JMS Broker
          jbertram

          Technically speaking either will work, but from a performance perspective the pooled-connection-factory will be quite a bit better.

          • 2. Re: Wildly 10 - Connection to an external JMS Broker
            vincent.sourin

            Justin,

             

            Thank you for your advice.

            Let me abuse your help a little bit more :-)

             

            The external broker to which I should produce a message is actually a cluster using udp to broadcast its connectors.

            From the way I understand it, a pooled-connection-factory in Wildfly requires using a "remote-destination-outbound-socket-binding" with host and port.

            Do you know if it is possible to use the UDP broadcast address to define the remote connector in Wildfly or do I need to know all the addresses/ports of the servers forming the cluster and list each of them in the connectors part of the pooled-connection-factory ?

             

            • 3. Re: Wildly 10 - Connection to an external JMS Broker
              jbertram

              You can configure the pooled-connection-factory to reference a discovery-group. The discovery-group you configure should use the same multicast address and port used by the broadcast-group on the cluster you wish to connect to.