[jboss-jira] [JBoss JIRA] (AS7-6408) Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT

Tue Jan 29 09:51:47 EST 2013

    [ https://issues.jboss.org/browse/AS7-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751077#comment-12751077 ] 

Tomaz Cerar commented on AS7-6408:
----------------------------------

I have found the issue and resolved it.

However this approach of sending protocol list as part of add operation on stack is deprecated and only works because validation of operations is disabled in CLI. (check jboss-cli.xml)
new approach is to call :add-protocol(type=<type>, socket-binding=<optional socket-binding>) operation for each protocol you are adding.
problem with old way is that you can only list protocols but you cannot define to witch socket-binding they relate...

old way will still work but if possible try to migrate your scripts to new model.

> 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