Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-176

Undefining attribute socket-binding or re-creating management interface leads to BindException: Address already in use

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • 8.0.0.Alpha1
    • None
    • Management
    • None

    Description

      1 - Assign a secure-socket-binding to management-interface=management-http:

       /core-service=management/management-interface=http-interface:write-attribute(name="secure-socket-binding", value="management-https")
      

      2- Try to remove the socket-binding (the HTTP one)

       
      /core-service=management/management-interface=http-interface:undefine-attribute(name="socket-binding")
      

      You receive an error:

       {
          "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
      }
      

      if you try to affect another socket binding, and then remove it, it works:

       
      [standalone@10.104.68.140:9999 /] /core-service=management/management-interface=http-interface:add(socket-binding=management-http2)
      {"outcome" => "success"}
      

      Also deleting the whole management-http interface and recreating fails with the same error

      Attachments

        Activity

          People

            bstansbe@redhat.com Brian Stansberry
            abenaiss Akram Ben Aissi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: