Migrate from #Wildfly 10 + external #ActiveMQ to #Wildfly 13 + embedded #Artemis

By | March 27, 2019

As I mentioned in a previous post I am a long time user of WildFly 10 and now in the process of upgrading to WildFly 13. Yes, not the latest version because I have some legacy source code constraints that forces me to not consider yet WildFly 14 and up.

WildFly 13 includes an Artemis implementation of the JMS engine. This means that all the internal JMS queues used by some enterprise applications no longer need to be defined in an external ActiveMQ server.

The following is a short tutorial on how to migrate your setup from Wildfly 10 + queues defined in ActiveMQ to WildFly 13 with queues defined in the included Artemis engine.

All the configurations are done in the standalone.xml configuration file from the wildfly/standalone/configuration directory.

I am going to explain the changes to each relevant section.

WildFly 10 configuration

Under WildFly 10 we needed to include a package with a resource addaptor to be able to access the external ActiveMQ server. The package I was using was activemq.rar from Maven central https://search.maven.org/search?q=a:activemq-rar

Under system-properties we needed to include it:

        <subsystem xmlns="urn:jboss:domain:ejb3:4.0">
                    <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
                <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/>
                <singleton default-access-timeout="5000"/>
                <resource-adapter-ref resource-adapter-name="activemq.rar"/>
                <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>

Then a section for the resource adaptor describing the configuration for the queues

        <subsystem xmlns="urn:jboss:domain:resource-adapters:4.0">
                <resource-adapter id="activemq.rar">
                    <config-property name="ServerUrl">
                    <config-property name="UserName">
                    <config-property name="Password">
                        <connection-definition class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory" jndi-name="java:/JmsXA" enabled="true" pool-name="ConnectionFactory">
                        <admin-object class-name="org.apache.activemq.command.ActiveMQQueue" jndi-name="java:/queue/startup" use-java-context="true" pool-name="startup">
                            <config-property name="PhysicalName">
                        <admin-object class-name="org.apache.activemq.command.ActiveMQQueue" jndi-name="java:/queue/mq.sys.dmq" use-java-context="true" pool-name="mq.sys.dmq">
                            <config-property name="PhysicalName">

Note that we had to define an URL to the external ActiveMQ server and credentials to connect to it.

Just 2 queues are defined in this example: startup (an application queue) and the dead message queue mq.sys.dmq

Note that activemq-broker-…jar and activemq-client-…jar libraries must be added in a library package under wildlfy/modules to be visible by wildfly.

WildFly 13 configuration

We no longer need to deploy an external resource adapter package. We just have to tell WildFly to import in the configuration the MQ engine module that comes with the release.

In the extension section make sure to include the following:

<server xmlns="urn:jboss:domain:7.0">
        <extension module="org.wildfly.extension.messaging-activemq"/>

Then simply define the queues as following:

        <subsystem xmlns="urn:jboss:domain:messaging-activemq:3.0">
            <server name="default">
                <security enabled="false"/>
                <management address="localhost" jmx-enabled="true" jmx-domain="org.apache.activemq.artemis"/>
                <security-setting name="#">
                    <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
                <address-setting name="#" dead-letter-address="queue/mq.sys.dmq" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10"/>
                <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/>
                <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput">
                    <param name="batch-delay" value="50"/>
                <in-vm-connector name="in-vm" server-id="0">
                    <param name="buffer-pooling" value="false"/>
                <http-acceptor name="http-acceptor" http-listener="default"/>
                <http-acceptor name="http-acceptor-throughput" http-listener="default">
                    <param name="batch-delay" value="50"/>
                    <param name="direct-deliver" value="false"/>
                <remote-acceptor name="internal-messaging-acceptor" socket-binding="internal-messaging"/>
                <in-vm-acceptor name="in-vm" server-id="0">
                    <param name="buffer-pooling" value="false"/>
                <jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>
                <jms-queue name="mq.sys.dmq" entries="java:/queue/mq.sys.dmq java:jboss/exported/queue/mq.sys.dmq"/>
                <jms-queue name="startup" entries="queue/startup java:jboss/exported/jms/queue/startup"/>
                <jms-queue name="dummy" entries="queue/dummy java:jboss/exported/jms/queue/dummy"/>
                <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
                <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/>
                <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>

Note that we do not have to specify any connection URL to the MQ server and no credentials to connect to it.

Just 2 queues are defined in this example: startup (an application queue) and the dead message queue mq.sys.dmq

There are two additional queues “ExpiryQueue” and “dummy” that are required by the application server.

This is all.

4 thoughts on “Migrate from #Wildfly 10 + external #ActiveMQ to #Wildfly 13 + embedded #Artemis

  1. Anonymous

    Estou com dúvidas. Utilizo atualmente a versão 13. No caso, alguém sabe as configurações exatas para estar realizando a recuperação de filas, ao reiniciar o WildFly?

  2. George Valentin Voina Post author

    I did not try this kind of setup (Wildfly 14 and artemis but as a external server.) but it should work the same as in the case of an external ActiveMq server. As you can see in the post the original setup using an external ActiveMq servers used the “resourse-adaptor” section to load the “client library” for the external ActiveMQ:

    <subsystem xmlns=”urn:jboss:domain:resource-adapters:4.0″>
    <resource-adapter id=”activemq.rar”>

    As Artemis is in fact e project that aims to replace Active MQ you should be able to do the same.
    Artemis also has a “client library” you can use as a resource adaptor in Wildfly config. See bellow:

    It could be that some parameters are different when configuring the Artemis resource adapter but this should be a start point for you.

  3. Janusz

    I have one question about this text. Currrently I’m using Wildfly 14 and I want use artemis but as a external server. How should I configure my Wildfly server to use existing extension and send and receive messages from remote JMS server?
    I will be grateful for your help.

    1. Alifi Augusto Estevam dos Santos

      Estou trabalhando com a versão 13. No caso, estou utilizando o journal-directory para recuperação de fila, quando o servidor é reiniciado. Porém estão vindo vazias, gerando quebra de código (nullpointerexception). Alguém sabe como me ajudar? Além disso, tem alguma documentação sobre?


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.