[jboss-jira] [JBoss JIRA] (AS7-3692) Management: jgroups add stack operation does not work

[ https://issues.jboss.org/browse/AS7-3692?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-3692: ------------------------------------------ The workaround here is to batch together the commands used to build the protocol stack: {noformat} [standalone@localhost:9999 /] batch [standalone@localhost:9999 / #] /subsystem=jgroups/stack=fred:add() #1 /subsystem=jgroups/stack=fred:add() [standalone@localhost:9999 / #] /subsystem=jgroups/stack=fred/transport=TRANSPORT:add(type=UDP) #2 /subsystem=jgroups/stack=fred/transport=TRANSPORT:add(type=UDP) [standalone@localhost:9999 / #] /subsystem=jgroups/stack=fred:add-protocol(type=MPING) #3 /subsystem=jgroups/stack=fred:add-protocol(type=MPING) [standalone@localhost:9999 / #] run-batch The batch executed successfully. {noformat} Unlike a cache container or a cache which can just be add()'ed and has an extensive system of defaults which make it a useable service straight away, an empty JGroups stack is not useable and really needs to have a transport and a minimal set of protocols added before it becomes useable as a group communication protocol. Consequently, although it is not made explicit, the add command assumes that a useable stack configuration is present for the command to succeed. Some discussion needs to happen on whether or not we do provide a full set of defaults for an empty add operation. The error message here definitely needs to be improved to reflect the fact that batching is required, certain protocol layers should be present, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira