Hi, > -----Original Message----- > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] > Sent: Monday, April 7, 2014 5:46 PM
> (...) > On my previously referenced test, I modified the hosts table to use > 127.0.0.10 for the localhost entry. Ping picked it up right away, but > reported > results were from 127.0.0.1, which I'm sure was probably because of the > initialized value pulled from the hosts table at boot. Did not try, do not > care, > but it might have replied from the 10 address after a reboot. That is because it seems any address from 127.0.0.1 to 127.255.255.254 may be used as loopback address - see [1]. E.g. if you "ping 127.2.3.4", you will get the same results as with 127.0.0.1. It would have surprised me if ping would report the results for a wrong IP address. As for the topic, I cannot help much, but I wanted to note that I'm also using the ISAPI Connector 1.2.39 (x64) on a Windows Server 2012 R2, but I did not encounter the reported issue. This is my workers.properties: # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8019 On that system, Tomcat listens on both [::]:8019 and 0.0.0.0:8019, and the ISAPI connector uses 127.0.0.1:8019 to connect to Tomcat. The "hosts" file on this system doesn't contain any entry. Regards, Konstantin Preißer [1] http://superuser.com/questions/393700/what-is-127-0-0-2-ip-address-for --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
