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

Bernd Koecke (JIRA) jira-events at lists.jboss.org
Wed Jan 30 03:07:57 EST 2013


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

Bernd Koecke commented on AS7-6408:
-----------------------------------

I pulled the newest changes and now the old way works.

You are right, the new way looks much more intuitive and I changed my scripts. I use :add-protocol and it works as you said, but the :add-transport operation is unknown. But :add-transport was not really part of this issue. Should I close the issue or should I look at the changes of my next pulls and wait until :add-transport appears?

Thanks a lot for your fast help and fix :)!

                
> 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


More information about the jboss-jira mailing list