[jboss-jira] [JBoss JIRA] (AS7-3863) jgroups protocol order not retained
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3863:
------------------------------------------
The two attributes here are:
(i) protocol, which is a child of stack and is provided by the model to support the
protocol definitions as child resources
(ii) protocols, which is a read-only attribute which maintains the order of the protocols
The problem here is that, IIUC, I have little or no control on how child resources are
stored as a data structure within the model.
I'll have to consult with Brian to see if there is a better way of handling this.
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@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