JMS destinations are not available

Even though we are deploying the src/test/resources/wildfly-tck-min.yml when starting wildfly, the destinations don't seem available. The only queue/topic deployment messages in the log are:

2024-08-23 01:49:11,861 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
2024-08-23 01:49:11,862 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
2024-08-23 01:49:11,862 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
2024-08-23 01:49:11,862 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
2024-08-23 01:49:11,886 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221034: Waiting indefinitely to obtain primary lock
2024-08-23 01:49:11,886 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221035: Primary Server Obtained primary lock
2024-08-23 01:49:12,324 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: Deploying ANYCAST queue jms.queue.ExpiryQueue on address jms.queue.ExpiryQueue
2024-08-23 01:49:12,327 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: Deploying ANYCAST queue jms.queue.DLQ on address jms.queue.DLQ

and any deployment with a queue/topic reference fails with:

2024-08-23 22:40:49,984 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly 33.0.0.Beta1-SNAPSHOT (WildFly Core 25.0.0.Beta4) started in 1956ms - Started 394 of 637 services (344 services are lazy, passive or on-demand) - Server configuration file in use: standalone-full.xml - Minimum feature stability level: community
2024-08-23 22:40:51,316 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/starksm/Dev/Jakarta/wildflytck-new/wildfly/dist/target/wildfly-33.0.0.Beta1-SNAPSHOT/standalone/data/content/17/2ce03bc6909d80d6869aaf146d5bb8b2bbac97/content
2024-08-23 22:40:51,325 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "closedQueueConnection_servlet_vehicle.ear" (runtime-name: "closedQueueConnection_servlet_vehicle.ear")
2024-08-23 22:40:51,694 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "closedQueueConnection_servlet_vehicle_web.war")
2024-08-23 22:40:51,947 WARN  [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0013: Deployment closedQueueConnection_servlet_vehicle.ear contains Jakarta Contexts and Dependency Injection annotations but no bean archive was found (no beans.xml or class with bean defining annotations was present).
2024-08-23 22:40:51,992 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "closedQueueConnection_servlet_vehicle.ear")]) - failure description: {
    "WFLYCTL0412: Required services that are not installed:" => [
        "jboss.naming.context.java.jms.QueueConnectionFactory",
        "jboss.naming.context.java.MY_QUEUE"
    ],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => [
        "service jboss.naming.context.java.module.closedQueueConnection_servlet_vehicle.closedQueueConnection_servlet_vehicle_web.env.jms.MyQueueConnectionFactory is missing [jboss.naming.context.java.jms.QueueConnectionFactory]",
        "service jboss.naming.context.java.module.closedQueueConnection_servlet_vehicle.closedQueueConnection_servlet_vehicle_web.env.jms.MY_QUEUE is missing [jboss.naming.context.java.MY_QUEUE]"
    ]
}
2024-08-23 22:40:51,993 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "closedQueueConnection_servlet_vehicle.ear")]) - failure description: {
    "WFLYCTL0412: Required services that are not installed:" => [
        "jboss.naming.context.java.jms.QueueConnectionFactory",
        "jboss.naming.context.java.MY_QUEUE"
    ],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => [
        "service jboss.naming.context.java.module.closedQueueConnection_servlet_vehicle.closedQueueConnection_servlet_vehicle_web.env.jms.MyQueueConnectionFactory is missing [jboss.naming.context.java.jms.QueueConnectionFactory]",
        "service jboss.naming.context.java.module.closedQueueConnection_servlet_vehicle.closedQueueConnection_servlet_vehicle_web.env.jms.MY_QUEUE is missing [jboss.naming.context.java.MY_QUEUE]"
    ]
}
2024-08-23 22:40:51,993 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "closedQueueConnection_servlet_vehicle.ear" was rolled back with the following failure message: 
{
    "WFLYCTL0412: Required services that are not installed:" => [
        "jboss.naming.context.java.jms.QueueConnectionFactory",
        "jboss.naming.context.java.MY_QUEUE"
    ],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => [
        "service jboss.naming.context.java.module.closedQueueConnection_servlet_vehicle.closedQueueConnection_servlet_vehicle_web.env.jms.MyQueueConnectionFactory is missing [jboss.naming.context.java.jms.QueueConnectionFactory]",
        "service jboss.naming.context.java.module.closedQueueConnection_servlet_vehicle.closedQueueConnection_servlet_vehicle_web.env.jms.MY_QUEUE is missing [jboss.naming.context.java.MY_QUEUE]"
    ]
}

jakartaredhat / wildfly-ee11-tck-runner

JMS destinations are not available #7