[
https://jira.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.plug...
]
Paul Ferraro commented on MODCLUSTER-168:
-----------------------------------------
We don't want to use InetAddress.getHostName() since this may perform unwanted reverse
dns lookup if the host was specified as an address.
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL:
https://jira.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira