[jboss-jira] [JBoss JIRA] (WFLY-2773) ClientConfigurationImpl should not translate IP address to host name
Jan Martiska (JIRA)
issues at jboss.org
Fri Jan 17 07:53:33 EST 2014
Jan Martiska created WFLY-2773:
----------------------------------
Summary: ClientConfigurationImpl should not translate IP address to host name
Key: WFLY-2773
URL: https://issues.jboss.org/browse/WFLY-2773
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Domain Management
Affects Versions: 8.0.0.CR1
Reporter: Jan Martiska
Assignee: Jan Martiska
When creating a ModelControllerClient and passing in an IP address, ClientConfigurationImpl internally translates it to a host name, like here:
{noformat}
public static ModelControllerClientConfiguration create(final InetAddress address, final int port) {
return new ClientConfigurationImpl(address.getHostName(), port, null, null, null, createDefaultExecutor(), true, null);
}
{noformat}
Later on, when the client connects, it is translated via DNS back to an IP address. This is not only unnecessary, but in some situations, it is wrong.
Consider a Windows machine having two IP addresses ,A and B, on one network interface, where only A is pointed at by a DNS record.
- Run AS testsuite and pass it the address B as the node0 property, AS will bind itself to this address.
- Now when a test creates a ModelControllerClient using IP address B, the address B will get translated to the host name, even though B is not in the DNS. The resolving works this way on a Windows machine.
- During the connection, the host name will get resolved by DNS to address A and the test will try to connect through address A. The connection will be refused, or worse, might connect to another instance on the same machine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list