From my point of view (aka console) it can be deferred. We are not
going to provide a UI for it with 7.1. But on the other hand, the actual model can be
considered public API and should not be subject to change once released to the public.
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.Final
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: