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

JMS queue resource is not found

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Blocker Blocker
    • None
    • 13.0.0.Beta1
    • Naming
    • None
    • Hide 
      git clone https://github.com/resteasy/Resteasy
cd Resteasy
mvn clean install -DfailIfNoTests=false -Dtest=InjectionTest -Dserver.home=/path/to/wildfly/home
      Show
      git clone https: //github.com/resteasy/Resteasy cd Resteasy mvn clean install -DfailIfNoTests= false -Dtest=InjectionTest -Dserver.home=/path/to/wildfly/home
    • Regression

      Deploying of [1] fails with following exception.

      org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy InjectionTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.InjectionTest.InjectionTest.env.jms.queue.test"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.InjectionTest.InjectionTest.env.\"org.jboss.resteasy.test.cdi.injection.resource.CDIInjectionResourceProducer\".bookQueue is missing [jboss.naming.context.java.module.InjectionTest.InjectionTest.env.jms.queue.test]"]}}}

      The deployment is part of Resteasy test suite. The same test works with Wildfly 12.

      Blocker priority was chosen because this is regression against Wildfly 12.

      User's impact: Some deployments can stop working after upgrade to Wildfly 13.

      I found out that the regression is caused by the commit WFLY-10358

      [1] https://github.com/resteasy/Resteasy/blob/master/testsuite/integration-tests/src/test/java/org/jboss/resteasy/test/cdi/injection/resource/CDIInjectionResourceProducer.java

              Unassigned Unassigned
              eduda_jira Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: