]
Kabir Khan commented on AS7-4468:
---------------------------------
Setting it in the reload-required state is a signal to the user that there are no
guarantees that the change results in a properly configured server, and that the affected
server should be restarted. This now happens following the remove call.
But now that you mention it, the new state should probably be reported in the individual
results. I'll take a look at what happens for a standalone server and adjust if
necessary.
Cannot remove and re-add socket-binding group
---------------------------------------------
Key: AS7-4468
URL:
https://issues.jboss.org/browse/AS7-4468
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Kabir Khan
Fix For: 7.1.2.Final-redhat1
Error message when trying to (remove and) add a socket-binding-group in domain mode:
First remove:
{ "operation" => "remove", "address" =>
[("socket-binding-group" => "standard-sockets")] }
Result:
{
"outcome" : "success",
"result" : null,
"server-groups" : {"server-group-1" : {"server-1" : {
"host" : "master",
"response" : {"outcome" : "success"}
}}}
}
Now add again:
{
"name" : "standard-sockets",
"default-interface" : "public",
"operation" : "add",
"address" : [{ "socket-binding-group" : "standard-sockets"
}]
}
Result:
{
"outcome" : "failed",
"result" : null,
"failure-description" : "JBAS010839: Operation failed or was rolled back
on all servers.",
"rolled-back" : true,
"server-groups" : {"server-group-1" : {"server-1" : {
"host" : "master",
"response" : { "outcome" : "failed",
"failure-description" : "JBAS014749: Operation handler failed: Service
jboss.socket-binding-manager is already registered", "rolled-back" : true
}
}}}
}
For me, this seems a bit strange. If an error shall be produced, then it should be thrown
when removing the socket-binding-group, as there is a server running referencing the
socket-binding-group via server-group. But if the socket-binding-group can be removed, it
should also be possible to add it again (possibly with new defined socket-bindings in the
group, then trigger a restart of the server in order to take the newly configured ports
into account).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: