jboss.ejb.default-resource-adapter-name-service wildfly 26

This is a follow up from my previous question: https://stackoverflow.com/staging-ground/79353883. I changed version of the Wildfly to 26 and transfered all the code and libraries to work with jakarta. When I tried to run my Wilfly server I got an error message: service jboss.ejb.default-resource-adapter-name-service not found. I tried to do what is described here: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found, but it triggered another error. I figured that I need to add messaging-activemq subsystem in my standalone.xml to provide the adapter name. However, the error shows up: WFLYCTL0362: Capabilities required by resource '/subsystem=messaging-activemq/server=default' are not available.

Here is the activemq subsystem code:

<subsystem xmlns="urn:jboss:domain:messaging-activemq:5.0">
<server name="default">
    <security-setting name="#">
        <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
    </security-setting>
    <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10"/>
    <http-acceptor name="http-acceptor" http-listener="default"/>
    <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="http"/>
    <jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>
    <jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>
    <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="http-connector">
        <credential-reference store="applicationKS" alias="localhost"/>
    </pooled-connection-factory>
</server>

And here is my standalone.xml for reference: (I removed extensions and management tags, so it will fit in the character limit)

<?xml version="1.0" ?>

jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE h2 sa sa org.h2.jdbcx.JdbcDataSource false ${jboss.bind.address:127.0.0.1}

    <subsystem xmlns="urn:jboss:domain:weld:4.0"/>
</profile>
<interfaces>
    <interface name="management">
        <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
    </interface>
    <interface name="public">
        <inet-address value="${jboss.bind.address:127.0.0.1}"/>
    </interface>
</interfaces>
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
    <socket-binding name="http" port="${jboss.http.port:8080}"/>
    <socket-binding name="https" port="${jboss.https.port:8443}"/>
    <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
    <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
    <socket-binding name="txn-recovery-environment" port="4712"/>
    <socket-binding name="txn-status-manager" port="4713"/>
    <outbound-socket-binding name="mail-smtp">
        <remote-destination host="${jboss.mail.server.host:localhost}" port="${jboss.mail.server.port:25}"/>
    </outbound-socket-binding>
</socket-binding-group>

I tried to remove all instances of "other" security domains in standalone, but error was the same. It could use some conflicting libraries, even though I checked capabilities and removed outdated libraries, this still might present an unforeseen issue. Thank you for your help!