11:08 a.m.
Heiko Braun created AS7-3863:
--------------------------------
Summary: 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: Brian Stansberry
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}
"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
11:10 a.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Heiko Braun updated AS7-3863:
-----------------------------
Description:
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}
was:
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}
"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}
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: Brian Stansberry
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
11:10 a.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Heiko Braun reassigned AS7-3863:
--------------------------------
Assignee: Richard Achmatowicz (was: Brian Stansberry)
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
11:12 a.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-3863:
----------------------------------
I can see that there is an extra attribute that expresses the protocol order:
{noformat}
[standalone@localhost:9999 /] /subsystem=jgroups/stack=tcp:read-attribute(name=protocols)
{
"outcome" => "success",
"result" => [
"MPING",
"MERGE2",
"FD_SOCK",
"FD",
"VERIFY_SUSPECT",
"BARRIER",
"pbcast.NAKACK",
"UNICAST2",
"pbcast.STABLE",
"pbcast.GMS",
"UFC",
"MFC",
"FRAG2"
]
}
{noformat}
but if would be desirable to retain the correct then read-resource is invoked.
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
3 p.m.
[
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
3:21 p.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Heiko Braun commented on AS7-3863:
----------------------------------
+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@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
3:25 p.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
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@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
5:03 p.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3863:
---------------------------------------
The data is stored in the model using LinkedHashMap semantics, insertion order rather than
last-read order. It may make sense to use a custom Resource impl for this to make it
easier to do things like insert in the middle.
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
10:58 p.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3863:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
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.2.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
12:28 a.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Kabir Khan reassigned AS7-3863:
-------------------------------
Assignee: Kabir Khan (was: Richard Achmatowicz)
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: Kabir Khan
Fix For: 7.1.2.Final-redhat1
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
12:19 p.m.
[
https://issues.jboss.org/browse/AS7-3863?page=com.atlassian.jira.plugin.s...
]
Kabir Khan commented on AS7-3863:
---------------------------------
The protocol children were in the right order but the read-resource handler was using an
undetermined order when assembling the model. AS7-4682 fixes that.
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: Kabir Khan
Fix For: 7.1.2.Final-redhat1
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
4385
days inactive
4454
days old
10 comments
5 participants
participants (5)
-
Brian Stansberry (JIRA) -
Heiko Braun (JIRA)
-
Jason Greene (JIRA)
-
Kabir Khan (JIRA)
-
Richard Achmatowicz (JIRA)