[
https://issues.jboss.org/browse/AS7-6408?page=com.atlassian.jira.plugin.s...
]
Bernd Koecke commented on AS7-6408:
-----------------------------------
Hello Tomaz,
thanks a lot for fixing this so fast :). I tried the :add-protocol operation and it works
like a charm.
But it works only when I'm using a batch run. When I send
/subsystem=jgroups/stack=udp:add(transport={"type"=>"UDP","socket-binding"=>"jgroups-udp"})
outside a batch, I get an error that the protocol list is missing. In earlier versions I
was able to define the protocol list like the transport attribute, it wasn't a list of
string. But it works well when I use :add-protocol lines after adding the stack and
putting a batch - run-batch around it.
I checked this with my current version, which doesn't include your fix. I will check
the old way, when I get your fix from git.
Thanks again,
Bernd
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
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