[jboss-jira] [JBoss JIRA] (AS7-2189) Revisit the jgroups management configuration
[
https://issues.jboss.org/browse/AS7-2189?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-2189:
-------------------------------------
Assignee: Richard Achmatowicz (was: Brian Stansberry)
Assigning to Richard, as he's working on clustering management stuff. But TBH I
don't think it's going to change much in 7.1. I believe Paul had some thoughts
about some higher level abstractions for the common use cases, but what you see above is
really what's involved. JGroups provides a tunable stack that people can and do
customize.
Revisit the jgroups management configuration
--------------------------------------------
Key: AS7-2189
URL: https://issues.jboss.org/browse/AS7-2189
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Assignee: Richard Achmatowicz
Fix For: 7.1.0.CR1
This doesn't look very reasonable to me:
{noformat}
[domain@localhost:9999 /] /profile=ha/subsystem=jgroups/stack=tcp:read-resource
{
"outcome" => "success",
"result" => {
"protocol" => [
{
"type" => "MPING",
"socket-binding" => "jgroups-mping"
},
{"type" => "MERGE2"},
{
"type" => "FD_SOCK",
"socket-binding" => "jgroups-tcp-fd"
},
{"type" => "FD"},
{"type" => "VERIFY_SUSPECT"},
{"type" => "BARRIER"},
{"type" => "pbcast.NAKACK"},
{"type" => "UNICAST"},
{"type" => "pbcast.STABLE"},
{"type" => "VIEW_SYNC"},
{"type" => "pbcast.GMS"},
{"type" => "UFC"},
{"type" => "MFC"},
{"type" => "FRAG2"},
{"type" => "pbcast.STREAMING_STATE_TRANSFER"},
{"type" => "pbcast.FLUSH"}
],
"transport" => {
"type" => "TCP",
"socket-binding" => "jgroups-tcp",
"diagnostics-socket-binding" => "jgroups-diagnostics"
}
}
}
{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