[
https://issues.jboss.org/browse/AS7-6408?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar edited comment on AS7-6408 at 1/30/13 8:06 AM:
-----------------------------------------------------------
Yeah fix also addresses that.
news for 7.2 is that you now have both :add-protocol and :add-transport operations that
replace lists parameters that ware part of add() operation
but in any case I would modify your script to something like that:
{noformat}
# Configuring jGroups
batch
/extension=org.jboss.as.clustering.jgroups:add
run-batch
batch
/subsystem=jgroups:add(default-stack=udp)
# protocols is a list of string now. I have to configure socket-bindings later
/subsystem=jgroups/stack=udp:add()
/subsystem=jgroups/stack=udp/transport=TRANSPORT:add("type"=>"UDP","socket-binding"=>"jgroups-udp")
/subsystem=jgroups/stack=udp:add-protocol("type"=>"FD_SOCK","socket-binding"=>"jgroups-udp-fd")
... (other protocols)...
/subsystem=jgroups/stack=tcp:add()
/subsystem=jgroups/stack=tcp/transport=TRANSPORT:add("type"=>"TCP","socket-binding"=>"jgroups-tcp")
/subsystem=jgroups/stack=tcp:add-protocol("type"=>"MPING","socket-binding"=>"jgroups-mping")
/subsystem=jgroups/stack=tcp:add-protocol("type"=>"pbcast.NAKACK2")
... (other protocols)...
run-batch
{noformat}
was (Author: ctomc):
Yeah fix also addresses that.
news for 7.2 is that you now have both :add-protocol and :add-transport operations that
replace lists parameters that ware part of add() operation
but in any case I would modify your script to something like that:
{noformat}
# Configuring jGroups
batch
/extension=org.jboss.as.clustering.jgroups:add
run-batch
batch
/subsystem=jgroups:add(default-stack=udp)
# protocols is a list of string now. I have to configure socket-bindings later
/subsystem=jgroups/stack=udp:add()
/subsystem=jgroups/stack=udp:add-transport("type"=>"UDP","socket-binding"=>"jgroups-udp")
/subsystem=jgroups/stack=udp:add-protocol("type"=>"FD_SOCK","socket-binding"=>"jgroups-udp-fd")
... (other protocols)...
/subsystem=jgroups/stack=tcp:add()
/subsystem=jgroups/stack=udp:add-transport("type"=>"TCP","socket-binding"=>"jgroups-tcp")
/subsystem=jgroups/stack=udp:add-protocol("type"=>"MPING","socket-binding"=>"jgroups-mping")
/subsystem=jgroups/stack=udp:add-protocol("type"=>"pbcast.NAKACK2")
... (other protocols)...
run-batch
{noformat}
Can't configure JGroups subsystem with CLI script in
7.2.0.Alpha1-SNAPSHOT
---------------------------------------------------------------------------
Key: AS7-6408
URL:
https://issues.jboss.org/browse/AS7-6408
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.2.0.Alpha1
Environment: Git checkout of JBossAS 7.2.0.ALPHA1 from today (28/Jan/2013)
Reporter: Bernd Koecke
Assignee: Tomaz Cerar
Fix For: 7.2.0.Alpha1
Attachments: standalone-ha-jgroups.cli, standalone-jgroups-fragment.xml
When I try to configure extension and subsystem JGroups with a CLI script, the attribute
"protocols" of the stack=tcp- or stack=udp-node contains the list of configured
protocols twice. The result is that the list of protocols is doubled in the
standalone.xml. But having a protocol twice in one stack results in an error at next
server startup. I will attach the CLI script and the resulting XML fragment.
When I shutdown the server, remove the doubled second part of each protocol list, the
server comes up and all is working fine. But I can't configure it only with a CLI
script.
--
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