Summary: | tomcat-connectors-1.2.39-windows-x86_64-iis does not resolve workers DNS names | ||
---|---|---|---|
Product: | Tomcat Connectors | Reporter: | Konstantin Kolinko <knst.kolinko> |
Component: | isapi | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christoph.kaser |
Priority: | P2 | ||
Version: | 1.2.39 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Attachments: | 2014-04-05_jk_56352_jkresolve_v1.patch |
Description
Konstantin Kolinko
2014-04-05 14:21:57 UTC
Created attachment 31484 [details]
2014-04-05_jk_56352_jkresolve_v1.patch
Patch for the issue (not tested).
The patch does nothing. JK_INET6 is defined as AF_INET6 The only thing that can be is the location of freeaddrinfo(ai_list); It's a clear bug. The reason is probably in the missing 127.0.0.1 localhost entry in the host file. Since the resolve code is now a copy from APR, the same behaviour exists with HTTPD for example. However there is still a bug with freeaddrinfo, so this could cause more serious problems. (In reply to Mladen Turk from comment #2) > The patch does nothing. JK_INET6 is defined as AF_INET6 OK. Good to know. I am just saying that it looks odd. > The only thing that can be is the location of freeaddrinfo(ai_list); > It's a clear bug. Thank you for fixing. (In reply to Mladen Turk from comment #3) > The reason is probably in the missing > 127.0.0.1 localhost > entry in the host file. Since the resolve code is now a copy from APR, the > same behaviour exists with HTTPD for example. If it fails to resolve the host name, I would expect some different behaviour rather than an attempt to connect to 0.0.0.0. (Just for a record: Apparently, adding such entry did not help http://markmail.org/message/pgzhzuwozcvxzab7 The problem seems to be solved with the new 1.2.40 release! Thanks for confirming. Closing. |