]
Kabir Khan commented on AS7-4468:
---------------------------------
This might need more work, I am checking with Brian.
The problem is that your 2) will currently cause the same error since I am not removing
the socket binding group as part of the remove operation. Removing that service has its
own problems since other services depend on that.
With what is there it would be possible to
1) remove the group
2) restart the server in admin-only mode
3) add the group
4) restart the server in normal mode
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: