Users of previous versions of JBoss EAP 6 may have found that servers were not able to reconnect to the Domain Controller after it was reloaded, if the managed servers were not restarted as well.
This issue occurred if the reverse IP lookup was incorrectly configured, meaning the servers were presented with the hostname of the Controller (and not its IP address) to reconnect to. In these situations the connection would fail.
This issue has been resolved in this release of the product by reusing the data stored in the `InetSocket` object. This avoids the need to do a reverse IP lookup and allows the servers to reconnect as expected.
This is a clone of https://issues.jboss.org/browse/WFLY-2785
It is to avoid doing DNS reverse lookup when reconnecting to server but use whatever we already have as a value in InetSocket object. Otherwise user may face problem when reverse IP resolution is not configured or configured improperly.
This also caused some problems running the testsuite on windows.
Is this ticket relevant to the JBoss EAP 6.2.1 Release Notes? If so, please mark it as such and provide draft text. I understand that it's currently at "New" status but as GA is February 5, I presume it's either already completed, or to be deferred until next CP.
*** Bug 1060271 has been marked as a duplicate of this bug. ***
https://github.com/jbossas/jboss-eap/pull/915 replaces 870
Verified on EAP 6.3.0.DR1.