0 Replies Latest reply on Aug 15, 2019 2:08 AM by bjorn.bohlin

    Wait for JMS configuration at startup of Wildfly 11.0.0.Final

    bjorn.bohlin

      Hello,

       

      We are receiving the following error during startup of Wildfly:

       

      2019-08-14 15:35:51.128 [ServerService Thread Pool -- 67] ERROR o.j.a.c.management-operation - WFLYCTL0013: Operation ("read-resource-description") failed - address: ([

          ("subsystem" => "messaging-activemq"),

          ("server" => "default"),

          ("pooled-connection-factory" => "activemq-ra"),

          ("statistics" => "pool")

      ]) - failure description: "WFLYCTL0030: No resource definition is registered for address [

          (\"subsystem\" => \"messaging-activemq\"),

          (\"server\" => \"default\"),

          (\"pooled-connection-factory\" => \"activemq-ra\"),

          (\"statistics\" => \"pool\")

      ]"

       

      It seems as if loading of the JMS configuration is not done when our war file is started.

      If starting the Wildfly server first and then adding the war with cli we do not get any errors, but when the war is deployed and wildfly is started with the war we see the error.

       

      I have read in another thread (activemq RAR): WFLYCTL0030 No resource definition is registered for address where the suggestion is to add a dependency in the deploy artifact.

      We have tried with adding dependency in jboss-deployment-structure.xm. :

      <?xml version="1.0" encoding="UTF-8"?>

      <jboss-deployment-structure>

          <deployment>

              <exclude-subsystems>

                  <subsystem name="logging" />

              </exclude-subsystems>

              <dependencies>

                  <module name="org.jboss.resteasy.resteasy-jaxrs" />

                  <module name="org.apache.activemq.artemis"/>

                  <module name="org.apache.activemq.artemis.ra"/>

              </dependencies>

          </deployment>

      </jboss-deployment-structure>

      But without success.

       

      Another odd thing is that the error in the log disappears if we add statistics-enabled="true" to the configuration of pooled-connection-factory in standalone-full.xml. (Setting it to false still generates error message...)

      <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa" statistics-enabled="true"/>

      We do not wish to use statistics however.

       

      Any help or suggestion is highly appreciated.

       

      Cheers,

      Björn