[ https://issues.jboss.org/browse/WFLY-1430?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-1430: ------------------------------------------- I'll provide an update of what is happening with the clustering-subsystem. 1. The organization of resources has changed to reflect EE module deployments. Previously we had this: {noformat} /subsystem=clustering-monitor /subsystem=clustering-monitor/channel=* /subsystem=clustering-monitor/channel=*/deployment=* {noformat} where channel=X represented a cache container on channel X and its attributes, and channel=X/deployment=Y represented a web session cache Y on a channel X. The problem here is that the deployments which contain the distributable web apps or the @Clustered SFSBs are not represented. These have now been added as part of the resource organization. Now the resources are organised as follows: {noformat} /subsystem=clustering-monitor /subsystem=clustering-monitor/channel=* /subsystem=clustering-monitor/channel=*/deployment=* /subsystem=clustering-monitor/channel=*/deployment=*/web=WEB /subsystem=clustering-monitor/channel=*/deployment=*/bean=* {noformat} Now, channel=X/deployment=Y represents a deployment Y on a channel X, channel=X/deployment=Y/web=WEB represents a web session cache used by a deployment Y on a channel X and channel=X/deployment=Y/bean=Z represents a bean session cache for a @Clustered bean Z used by a deployment Y on a channel X. The idea here is that if users are interested in their clustered application deployment, they can navigate to the web session caches and or SFSB session caches by choosing the appropriate deployment name. 2. A ClusteredDeploymentRepository has been added It is not easy to pick up EE module deployment information using the service registry alone, so I wrote a deployment processor for the clustering-monitor subsystem which populated its own repository of clustered deployment information. So when the clustering-monitor subsystem starts up, it creates a service called ClusteredDeploymentRepository and also installs a deployment processor which populates the repository with information. Whenever a deployment happens, the deployment processor inspects the deployment and , if clustered, stores relevant information(in this case container and cache information for session caches) in the repository. The resource handlers for the clustering subsystem access that repository in order to find out which resources exist for deployment=Y, web=WEB and bean=Z resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira