Removal of messaging-activemq's server stops Infinispan services ---------------------------------------------------------------- Key: WFLY-7384 URL: https://issues.jboss.org/browse/WFLY-7384 Project: WildFly Issue Type: Bug Components: Clustering, JMS Reporter: Jeff Mesnil Assignee: Paul Ferraro Attachments: WFLY-7384.diff This issue occurs after I fixed the issue for WFLY-7333 which ensures that all services related to a messaging-activemq server are stopped when the server is removed. When I run the command to remove the server: /subsystem=messaging-activemq/server=default:remove I see logs in the app server about Infinispan services being stopped: {noformat} 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel server 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000080: Disconnecting JGroups channel hibernate 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000080: Disconnecting JGroups channel web 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel server 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000082: Stopping the RpcDispatcher for channel web 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000082: Stopping the RpcDispatcher for channel hibernate 09:28:46,381 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.4.0 [c96316a7-9b4d-11e6-ab8c-b8f6b112daf7] stopped, uptime 18.904 seconds {noformat} There should be no reason than stopping the messaging server should stop such Infinispan services. The messaging-activemq subsystem has *no* dependency to Infinispan resources. However both messaging-activemq and infinispan resources depends on JGroups resources. I did a diff of the services dump before and after removing the messaging-activemq server (see attached file). The Infinispan services are stopped as a consequence of stopping the jboss.messaging-activemq.default service. Before removing the server, this service is in this state: {noformat} Service \"jboss.messaging-activemq.default\" (class org.wildfly.extension.messaging.activemq.ActiveMQServerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: org.wildfly.management.jmx, org.wildfly.clustering.jgroups.default-channel-factory, jboss.outbound-socket-binding.http, jboss.binding.http, jboss.http-upgrade-registry.default, jboss.path.manager, jboss.security.security-domain.other) {noformat} The only relation between this messaging server and the Infinispan resources is that they depend on the org.wildfly.clustering.jgroups.default-channel-factory service. Before removing the messaging server, this service is in the state: {noformat} Service \"org.wildfly.clustering.jgroups.default-channel-factory\" (class org.jboss.msc.service.ValueService) mode PASSIVE state UP (parent: jboss.as.server-controller) (dependencies: org.wildfly.clustering.jgroups.channel-factory.ee) {noformat} After removing the messaging server, this service is in the state: {noformat} > Service \"org.wildfly.clustering.jgroups.default-channel-factory\" (class org.jboss.msc.service.ValueService) mode PASSIVE state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: org.wildfly.clustering.jgroups.channel-factory.ee) {noformat} I am not sure to understand why and when removing the jboss.messaging-activemq.default implies to remove the org.wildfly.clustering.jgroups.default-channel-factory service but there is no reason that removing any messaging-activemq resources should impact the state of Infinispan services