[
https://issues.jboss.org/browse/AS7-3575?page=com.atlassian.jira.plugin.s...
]
Michael Voegele commented on AS7-3575:
--------------------------------------
I get the same 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).
Socket-binding-group add operation does not work
------------------------------------------------
Key: AS7-3575
URL:
https://issues.jboss.org/browse/AS7-3575
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
Fix For: 7.1.2.Final-redhat1
The socket-binding-group add operation does not work. Add operation fails with the
error:
11:25:35,087 ERROR [org.jboss.as.controller.management-operation]
(management-handler-threads - 8) JBAS014612: Operation ("add") failed - address:
([("socket-binding-group" => "test-sockets")]):
org.jboss.msc.service.DuplicateServiceException: Service jboss.socket-binding-manager is
already registered
at
org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
Steps to reproduce:
1) start standalone server
2) connect via CLI
3)
[standalone@localhost:9999 /]
/socket-binding-group=test-sockets:add(default-interface="public")
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed:
Service jboss.socket-binding-manager is already registered",
"rolled-back" => true
}
--
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