[jboss-jira] [JBoss JIRA] (AS7-3863) jgroups protocol order not retained

[Heiko Braun (JIRA)]

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

Heiko Braun edited comment on AS7-3863 at 2/22/12 9:24 AM:
-----------------------------------------------------------

+1 

that would be great. although I manage to workaround this problem in the console, the problem will a burden for any other client. it's very confusing to "know" the list needs to be ordered , but then return it without any order. the second property works for programmatic access, but fails for humans.
                
      was (Author: heiko.braun):
    +1 

that would be great. although I manage to workaround this problem in the console, this core problem will a burden for any other client. furthermore it's very confusing to "know" the list needs to be ordered , but then return it without any order. the second property works for programmatic access, but fails for humans.
                  
> jgroups protocol order not retained
> -----------------------------------
>
>                 Key: AS7-3863
>                 URL: https://issues.jboss.org/browse/AS7-3863
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Richard Achmatowicz
>             Fix For: 7.1.1.Final
>
>
> the xml config:
> {noformat}
> <stack name="tcp">
>                 <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/>
>                 <protocol type="MPING" socket-binding="jgroups-mping"/>
>                 <protocol type="MERGE2"/>
>                 <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
>                 <protocol type="FD"/>
>                 <protocol type="VERIFY_SUSPECT"/>
>                 <protocol type="BARRIER"/>
>                 <protocol type="pbcast.NAKACK"/>
>                 <protocol type="UNICAST2"/>
>                 <protocol type="pbcast.STABLE"/>
>                 <protocol type="pbcast.GMS"/>
>                 <protocol type="UFC"/>
>                 <protocol type="MFC"/>
>                 <protocol type="FRAG2"/>
>             </stack>
> {noformat}
> the DMR response:
> {noformat}
> [standalone at localhost:9999 /] /subsystem=jgroups/stack=tcp:read-resource
> [...]
> "protocol" => {
>             "FD_SOCK" => undefined,
>             "FD" => undefined,
>             "VERIFY_SUSPECT" => undefined,
>             "BARRIER" => undefined,
>             "FRAG2" => undefined,
>             "MERGE2" => undefined,
>             "pbcast.GMS" => undefined,
>             "UNICAST2" => undefined,
>             "UFC" => undefined,
>             "MFC" => undefined,
>             "pbcast.NAKACK" => undefined,
>             "pbcast.STABLE" => undefined,
>             "MPING" => undefined
>         },
> {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