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

LocalTransactionTestCase failure when running under -Dts.layers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 27.0.0.Final
    • None
    • JMS, Test Suite
    • None
    • ---
    • ---

      The test case LocalTransactionTestCase is failing when run under -Dts.layers in the ejb-remote-broker-layers.surefire execution.

      JndiLookupMessagingDeploymentTestCase possibly has the same issue.

      The error reported is:

      [ERROR] org.jboss.as.test.integration.messaging.jms.naming.JndiLookupMessagingDeploymentTestCase  Time elapsed: 0.121 s  <<< ERROR!                      
      java.lang.RuntimeException: java.lang.RuntimeException: WFLYCTL0158: Operation handler failed: java.lang.NullPointerException
              at org.jboss.as.arquillian.container.ManagementClient.getProtocolMetaData(ManagementClient.java:284)
              at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:257)
              at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:151)
              at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:118)
              at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:239)
              at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:118)
              at jdk.internal.reflect.GeneratedMethodAccessor70.invoke(Unknown Source)
      

      The cause is this NullPointerException:

      amp#27;[0m&amp#27;[31m11:42:22,265 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
          ("deployment" => "LocalTransactionTestCase.war"),
          ("subsystem" => "messaging-activemq"),
          ("pooled-connection-factory" => "LocalTransactionTestCase_LocalTransactionTestCase_java_module/CF_allow_local_tx")
      ]): java.lang.NullPointerException
          at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryConfigurationRuntimeHandler.executeReadAttribute(PooledConnectionFactoryConfigurationRuntimeHandler.java:47)
          at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryConfigurationRuntimeHandler.executeReadAttribute(PooledConnectionFactoryConfigurationRuntimeHandler.java:34)
      

      After deployment a recursive read-resource is called:

      {
          "operation" => "read-resource",
          "address" => [
              ("deployment" => "LocalTransactionTestCase.war"),
              ("subsystem" => "*")
          ],
          "recursive-depth" => 2,
          "include-runtime" => true,
          "operation-headers" => {
              "caller-type" => "user",
              "access-mechanism" => "NATIVE"
          }
      }
      

      But the attribute that fails is:

      {
          "operation" => "read-attribute",
          "address" => [
              ("deployment" => "LocalTransactionTestCase.war"),
              ("subsystem" => "messaging-activemq"),
              ("pooled-connection-factory" => "LocalTransactionTestCase_LocalTransactionTestCase_java_module/CF_allow_local_tx")
          ],
          "name" => "enable-amq1-prefix",
          "include-defaults" => true,
          "resolve-expressions" => false,
          "include-undefined-metric-values" => false,
          "operation-headers" => {
              "caller-type" => "user",
              "access-mechanism" => "NATIVE"
          }
      }
      

              ehugonne1@redhat.com Emmanuel Hugonnet
              darran.lofthouse@redhat.com Darran Lofthouse
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: