[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-3791: ------------------------------------------ Heiko The approach for adding protocols: {noformat} $ batch $ /subsystem=jgroups/stack=tcp:add() $ /subsystem=jgroups/stack=tcp/transport=TRANSPORT:add(type=tcp, socket-binding=..., ...) $ /subsystem=jgroups/stack=tcp:add-protocol(type=MPING, socket-binding=..., ...) $ # continue to add protocols to the ordeered list - additions occur at the end only $ run-batch {noformat} There should be a read-write handler for each protocol resource, but no add handler. -- 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

[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-3791: ---------------------------------- is the order important? -- 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

[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-3791: ----------------------------- Summary: Cannot add/remove stack, protocols (was: Cannot add/remove stack protocols) -- 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

[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-3791: ---------------------------------- I cannot add a stack: {noformat} [standalone@localhost:9999 /] /subsystem=jgroups/stack=TCP:add() { "outcome" => "failed", "failure-description" => "JBAS014746: type may not be null", "rolled-back" => true } {noformat} -- 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

[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-3791: ---------------------------------- ok, seems to be case sensitive: {noformat} [standalone@localhost:9999 /] /subsystem=jgroups/stack=tcp:add() { "outcome" => "failed", "failure-description" => "JBAS014803: Duplicate resource [ (\"subsystem\" => \"jgroups\"), (\"stack\" => \"tcp\") ]", "rolled-back" => true } {noformat} but if the stack types are predefined, what are the allowed values? -- 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

[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz edited comment on AS7-3791 at 2/21/12 11:12 AM: -------------------------------------------------------------------- The stack names are not predefined, you should be able to create a stack using any name. However, the type attribute, both for the transport add operation {noformat} /subsystem=jgroups/stack=fred/transport=TRANSPORT:add(type=udp) {noformat} and for the protocol add opertation {noformat} /subsystem=jgroups/stack=fred:add-protocol(type=MPING) {noformat} are predefined, up to a point. The values for the transport are from a set {udp, tcp, tunnel} and the values for the latter are a larger set {mping, ping, frag, ...} which are the set of allowable JGroups protocol layers (version dependent). The problem with setting up validators for these attributes is that they rule out users supplying their own custom protocol layers, so we decided against validating them. The problem of creating stacks is described in the linked issue. was (Author: rachmato): The stack names are not predefined, you should be able to create a stack using any name. However, the type attribute, both for the transport add operation {noformat} /subsystem=jgroups/stack=fred/transport=TRANSPORT:add(type=udp) {noformat} and for the protocol add opertation {noformat} /subsystem=jgroups/stack=fred/add-protocol(type=MPING) {noformat} are predefined, up to a point. The values for the transport are from a set {udp, tcp, tunnel} and the values for the latter are a larger set {mping, ping, frag, ...} which are the set of allowable JGroups protocol layers (version dependent). The problem with setting up validators for these attributes is that they rule out users supplying their own custom protocol layers, so we decided against validating them. The problem of creating stacks is described in the linked issue. -- 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

[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-3791: ----------------------------- Comment: was deleted (was: well, see my comment above: "The stack names are not predefined, you should be able to create a stack using any name." this doesn't work.) -- 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

[ https://issues.jboss.org/browse/AS7-3791?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-3791: ------------------------------------------ The problem here is that the error message is too cryptic. What is happening is that if you try to create a stack via the add() operation *without* having specified a transport element and a non-empty protocol stack, either as optional parameters or via batching (see below), the runtime will try to install the transport element anyway, and will complain that its required parameter "type" describing the name of the transport protocol (i.e. udp, tcp, tunnel) may not be null. This is the message we are seeing. In order to specify a stack's transport and protocol list, there are two methods: - create the stack with one call to add() and specify them as optional parameters to the add operation, which now accepts transport and protocols parameters (see the operation description for add) - create the stack in several steps using batching, as described above I think this can be cleared up by checking if the transport element is undefined , or the protocol list is empty, and outputting a message something like: "stack transport element is undefined - please specify a transport and protocol stack, either as optional parameters to the add operation or via batching". -- 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