A number of integration tests start up external processes of various types (databases, ORBs, JMX servers) and then WildFly server under test connects to them. Sometimes the test isn't explicitly declaring the interface to which the process should bind, which increases the potential for environmental issues, i.e. if the process binds to an interface with which the WF server process can't communicate. This looks to be the cause of many of the failures in WFLY-18780.

Make this more robust by binding these processes to the same interface as the WF server itself.