Undefining attribute socket-binding or re-creating management interface leads to BindException: Address already in use ---------------------------------------------------------------------------------------------------------------------- Key: AS7-6771 URL: https://issues.jboss.org/browse/AS7-6771 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Akram Ben Aissi Assignee: Brian Stansberry Fix For: 8.0.0.Alpha1 1 - Assign a secure-socket-binding to management-interface=management-http: {code} /core-service=management/management-interface=http-interface:write-attribute(name="secure-socket-binding", value="management-https") {code} 2- Try to remove the socket-binding (the HTTP one) {code} /core-service=management/management-interface=http-interface:undefine-attribute(name="socket-binding") {code} You receive an error: {code} { "outcome" => "failed", "failure-description" => {"JBAS014671: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use /10.104.68.140:9990 Caused by: java.net.BindException: Address already in use"}}, "rolled-back" => true } {code} if you try to affect another socket binding, and then remove it, it works: {code} [standalone@10.104.68.140:9999 /] /core-service=management/management-interface=http-interface:add(socket-binding=management-http2) {"outcome" => "success"} {code} Also deleting the whole management-http interface and recreating fails with the same error