[
https://issues.jboss.org/browse/AS7-1989?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-1989:
----------------------------------------
It has to be socket-binding-group. And it should complain about a not supported property,
i.e. socket-group. Actually, it's a regression. I'm gonna look into this.
[domain@localhost:9999 /]
/server-group=my:add(profile=ha,socket-binding-group=ha-sockets)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => undefined
}
}
[domain@localhost:9999 /] /server-group=my:read-resource
{
"outcome" => "success",
"result" => {
"deployment" => undefined,
"jvm" => undefined,
"management-subsystem-endpoint" => false,
"profile" => "ha",
"socket-binding-group" => "ha-sockets",
"system-property" => undefined
}
}
Reading a server group resource in the CLI doesn't show the
socket group
------------------------------------------------------------------------
Key: AS7-1989
URL:
https://issues.jboss.org/browse/AS7-1989
Project: Application Server 7
Issue Type: Bug
Components: CLI
Environment: Fedora 15, Bash, very recent AS trunk.
Reporter: Misty Stanley-Jones
Assignee: Alexey Loubyansky
Priority: Minor
I added a server group using the following command:
[domain@localhost:9999 /]
/server-group=clustered-group:add(profile=ha,socket-group=ha-sockets)
I then used the following command to read the resource:
[domain@localhost:9999 /] /server-group=clustered-group:read-resource
{
"outcome" => "success",
"result" => {
"deployment" => undefined,
"jvm" => undefined,
"profile" => "ha",
"system-property" => undefined
}
}
It shows the profile but not the socket binding group. It seems like it should show both.
--
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