Hi all, I'm stunned about the enormous response to my question and I'm so sorry about the long delay of my answer now - but there is a world outside with household chores at the weekend. I'll try to answer the questions from the oldest to the youngest:
> Ok, another check in a command window (and I assume that you open this > command > window *on the server itself* where mod_jk and Tomcat are running, right ?) Definitively ;-) I stumbled on this problem on a server (Windows Server 2008 R2), then tried it on my workstation (Windows 7) which has the same configuration for Tomcat and IIS (and and where it doesn't work either). On the server I had no logfile. > test : > 1) telnet localhost 8009 > 2) telnet 127.0.0.1 8009 With "worker.ajp13w.host=localhost" 1) No answer (windows telnet: black console; cygwin telnet: no action, new prompt) 2) No answer (windows telnet: black console; cygwin telnet: no action, new prompt) With "worker.ajp13w.host=127.0.0.1" 1) No answer (windows telnet: black console; cygwin telnet: no action, new prompt) 2) No answer (windows telnet: black console; cygwin telnet: no action, new prompt) telnet doesn't work at all, no connection to any server on the local pc, in the intranet or internet (perhaps a firewall/proxy/ntlm setting). > Could this be an interaction between IPv4 and IPv6? Try: > C:> nslookup localhost nslookup localhost Server: dns.xyz.local Address: a.b.c.d Non-authoritative answer: Name: localhost.domainname.local Address: 127.0.0.1 > If only by curiosity, maybe Jessica-Aileen could try > worker.ajp13w.host=localhost. That doesn't make a difference. It doesn't work. > Jessica-Aileen, can you enable mod_jk's DEBUG logging? It might be > instructive > to see what it's trying to load when you give it "localhost". I haven't > checked > the code, but it might tell us what's going on with its name resolution. See attachment. By the way: The description of "prefer_ipv6" is unclear. I used " worker.ajp13w.prefer_ipv6=0", but the omission doesn't make a difference. It doesn't work either. > For the OP's specific problem, she need to see how "localhost" is resolving. > Most systems define it in the local "hosts" file, either /etc/hosts (*nix) > or > c:\Windows\system32\etc\hosts. There is _no_ _entry_ in the hosts file, it is commented out - which is the _default_ for Windows! See http://serverfault.com/questions/4689/windows-7-localhost-name-resolution-is-handled-within-dns-itself-why # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost Regards, Jessica
isapi_redirect.log
Description: Binary data
smime.p7s
Description: S/MIME cryptographic signature
