[ https://issues.jboss.org/browse/AS7-4388?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-4388: ------------------------------------------ Bela, thanks for the feedback! Paul also suggested creation of a separate subsystem. It does have its advantages: re-enforces that the JGroups and Infinispan subsystems represent local resources only and to see the global (different) view you need to look in a different place; allows those subsystems to stay relatively uncomplicated; can be optionally included in a profile). This would probably be a more intuitive presentation of cluster information as far as the user is concerned. As for probe, I did review all of its features (keys). Because it allows destructive operations (e.g. invoke an arbitrary operation on a protocol layer), I think we need to wait until we have some security mechanisms in place (AS8) before using it generally. But that probably does not prevent us from presenting a subset of keys for use. These could be presented as operations under /subsystem=cluster/name=session-cluster/channel=*. Also, it seems to require receiving commands by multicast, so will there not be a problem with TCP stacks? Perhaps make it available if the stack is UDP and mcast-enabled only? -- 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