[jboss-jira] [JBoss JIRA] (WFLY-9746) Revert JGroups capability reference to ChannelFactory

Revert JGroups capability reference to ChannelFactory ----------------------------------------------------- Key: WFLY-9746 URL: https://issues.jboss.org/browse/WFLY-9746 Project: WildFly Issue Type: Bug Components: Clustering, JMS Affects Versions: 12.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Blocker There is regression If Artemis is configured to JGroups tcp stack to form cluster then server does not start and fail with: {code} 13:24:02,424 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12) 13:24:02,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "messaging-activemq"), ("server" => "default") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => [ "jboss.messaging-activemq.default", "org.wildfly.clustering.command-dispatcher-factory.tcp" ], "WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.messaging-activemq.default.jms.manager is missing [jboss.messaging-activemq.default]", "jboss.messaging-activemq.default is missing [org.wildfly.clustering.command-dispatcher-factory.tcp]" ] } 13:24:02,438 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.messaging-activemq.default (unavailable) dependents: [service jboss.messaging-activemq.default.jms.manager] service org.wildfly.clustering.command-dispatcher-factory.tcp (missing) dependents: [service jboss.messaging-activemq.default] 13:24:02,485 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:11990/management 13:24:02,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:11990 {code} Configuration of jgroups and messaging-activemq subsystem: {code} <subsystem xmlns="urn:jboss:domain:jgroups:5.0"> <channels default="ee"> <channel name="ee" stack="udp" cluster="ejb"/> </channels> ... <stack name="tcp"> <transport type="TCP" socket-binding="jgroups-tcp"/> <protocol type="org.jgroups.protocols.TCPPING"> <property name="port_range"> 10 </property> <property name="num_initial_members"> 1 </property> <property name="initial_hosts"> 127.0.0.1[9600] </property> <property name="timeout"> 3000 </property> </protocol> <protocol type="MERGE3"/> <protocol type="FD_SOCK"/> <protocol type="FD"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK"/> <protocol type="UNICAST3"/> <protocol type="pbcast.STABLE"/> <protocol type="pbcast.GMS"/> <protocol type="UFC"/> <protocol type="MFC"/> <protocol type="FRAG2"/> <protocol type="RSVP"/> </stack> </stacks> </subsystem> .... <subsystem xmlns="urn:jboss:domain:messaging-activemq:3.0"> <server name="default" persistence-enabled="true" id-cache-size="200000"> <broadcast-group name="bg-group1" jgroups-stack="tcp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/> <discovery-group name="dg-group1" jgroups-stack="tcp" jgroups-channel="udp" refresh-timeout="10000"/> <cluster-connection name="my-cluster" address="jms" connector-name="connector" check-period="30000" connection-ttl="60000" call-timeout="30000" discovery-group="dg-group1"/> ... </server> </subsystem> {code} Attaching the whole config: standalone-full-ha.xml