Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-2490

Fail to run xpaasqe jms xa-load test with eap7 image based on the most up-to-date code of cct_module

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • None
    • None
    • Test Suite
    • None
      • build eap7 image from the most up-to-date cct_module
      • run the test with the module

    Description

      There are failures to the test EAP7JMSXARecoveryLoadTest with the eap7[1] image (eap71-dev branch) built on top of the image created from the most up-to-date cct_module[2] of branch master.

      When run mvn clean test -Ptest-eap -Peap7 -Dtest=EAP7JMSXARecoveryLoadTest#testJvmKillAndScaleDownToTwo -Dutilities.version=0.7-SNAPSHOT -Dtest.script.debug the server starts to fail with

      10:36:05,924 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.messaging-activemq.default: org.jboss.msc.service.StartException in service jboss.messaging-activemq.default: WFLYMSGAMQ0033: Failed to start service
              at org.wildfly.extension.messaging.activemq.ActiveMQServerService.start(ActiveMQServerService.java:359)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
              at java.lang.Thread.run(Thread.java:748)
      Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYMSGAMQ0030: Failed to find SocketBinding for connector: http-connector
              at org.wildfly.extension.messaging.activemq.ActiveMQServerService.start(ActiveMQServerService.java:216)
              ... 5 more
      

      This is probably caused by the fact the test deploys its own standalone-openshift.xml configuration which differs from changes done in the cct_module. There is specifically fix for CLOUD-2282 (https://github.com/jboss-openshift/cct_module/commit/2ffd4f736b5f0367d2d8ea3e5c6a010e93429c3e) which brings the incompatibility with the settings used in the test itself. The name of the endpoint of the messaging http-connector is from now http-messaging (https://github.com/jboss-openshift/cct_module/blob/master/os-eap7-launch/added/launch/activemq-subsystem.xml#L6)

      [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/
      [2] https://github.com/jboss-openshift/cct_module

      Attachments

        Activity

          People

            tremes1@redhat.com Tomas Remes
            ochaloup@redhat.com Ondrej Chaloupka (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: