Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <533DD41E.5020504@christopherschultz.net>
Date: Thu, 03 Apr 2014 17:35:26 -0400
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: AW: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does not
 work
References: <F3A2D2C96F17264D910CB93778C48427568F05FF@ZMBX04.bgr.local>
 <533C2161.9050900@ice-sa.com>
 <F3A2D2C96F17264D910CB93778C48427568F079C@ZMBX04.bgr.local>
 <533D63B2.6020100@ice-sa.com>
 <F3A2D2C96F17264D910CB93778C48427568F07DA@ZMBX04.bgr.local>
 <533DB7AA.5050600@ice-sa.com>
In-Reply-To: <533DB7AA.5050600@ice-sa.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

André,

On 4/3/14, 3:34 PM, André Warnier wrote:
> Alten, Jessica-Aileen wrote:
>>> -----Ursprüngliche Nachricht----- Von: André Warnier
>>> [mailto:aw@ice-sa.com] Gesendet: Donnerstag, 3. April 2014
>>> 15:36 An: Tomcat Users List Betreff: Re: AW:
>>> tomcat-connectors-1.2.39-windows-x86_64-iis does not work
>>> 
>>> Alten, Jessica-Aileen wrote:
>>>>> A bit guessing here :
>>>>> 
>>>>> You have :
>>>>>> worker.ajp13w.host=localhost
>>>>> 
>>>>> and
>>>>> 
>>>>>> jk_open_socket::jk_connect.c (735): connect to
>>>>>> 0.0.0.0:8009
>>> failed
>>>>>> (errno=49)
>>>>> is "localhost" == 0.0.0.0  ?
>>>>> 
>>>>> From the point of view of mod_jk/isapi, should it not be
>>> "127.0.0.1" ?
>>>> Your answer points to the right direction. 0.0.0.0 means: any
>>>> configured IPv4-Address on this computer, see
>>>> 
>>>> http://serverfault.com/questions/78048/whats-the-difference-between-
>>>
>>>> 
ip
>>>> -addre ss-0-0-0-0-and-127-0-0-1
>>>> 
>>>> In principle this is ok at first. The Ajp13 Connector was
>>>> configured in server.xml to listen at any IPv4 address on
>>>> port 8009 - which is the default setting. But the connector
>>>> can't find any suitable
>>> address.
>>>> The problem is: The new Tomcat-Connector can't parse 
>>>> "worker.ajp13w.host=localhost", instead localhost must be
>>>> replaced with "127.0.0.1", this works!
>>>> 
>>>> In my eyes this is a big fat bug, because most documentation
>>>> on workers use "localhost". localhost is actually the default
>>>> for the "host" connection directive.
>>>> 
>>>> The new worker directive "prefer_ipv6" doesn't change this
>>>> behavior.
>>>> 
>>> Hi.
>>> 
>>> Can you please really check this ?
>>> 
>>> Open a command window on that server, and do "ping localhost". 
>>> It should tell you what it understands by "localhost". Copy and
>>> paste the result here :
>> 
>> ping localhost
>> 
>> Ping wird ausgeführt für xyz.uv.local [127.0.0.1] mit 32 Bytes
>> Daten: Antwort von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128 Antwort
>> von 127.0.0.1: Bytes=32 Zeit<1ms TTL=128 Antwort von 127.0.0.1:
>> Bytes=32 Zeit<1ms TTL=128 Antwort von 127.0.0.1: Bytes=32
>> Zeit<1ms TTL=128
>> 
>> Ping-Statistik für 127.0.0.1: Pakete: Gesendet = 4, Empfangen =
>> 4, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: 
>> Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms
>> 
>> 
> That /is/ bizarre.  As far as I know, to resolve hostnames in its 
> configuration, mod_jk/isapi is using the OS's resolver library, the
> same as the one "ping" should be using. On the other hand, you say
> that if you have
> 
>>>>>> worker.ajp13w.host=localhost
> 
> it doesn't work (mod_jk cannot connect to tomcat), but when you
> change this to
> 
>>>>>> worker.ajp13w.host=127.0.0.1
> 
> then it works fine.
> 
> 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 ?)
> 
> test :
> 
> 1) telnet localhost 8009
> 
> 2) telnet 127.0.0.1 8009
> 
> Any difference between these 2 cases ?
> 
> If not, then indeed it looks like a mod_jk/isapi_redirect 1.2.39
> problem.
> 
> In any case, you cannot "connect to" 0.0.0.0, as this log line
> would suggest :
> 
>>>>>> jk_open_socket::jk_connect.c (735): connect to
>>>>>> 0.0.0.0:8009
>>> failed

Could this be an interaction between IPv4 and IPv6? Try:

C:> nslookup localhost

You might get only 127.0.0.1 or you might also get :: (or something
equivalent). I'm not sure why it wasn't happening with earlier
versions of mod_jk (which?).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTPdQeAAoJEBzwKT+lPKRY6i4P/jv+ozeg+saTWEDwWeR769JQ
1d3Y3n9Cnvk5qHlvEkTxOzu72MdUtl3+eLLgCT+7QNRQWr3m/Lj+vlN8E+M0d/6X
BWs8/XDP3fMyc6eBgQiTQWTZUMH1sGua4ceJ24PLviK1Pq9jambFeHHvdYluDK4K
ItgDyfXf9GkO5SsMvQxcic2VpjPxkPwM6W3ndjvDGYAucwK3ZW5FQTZ0GAsmvYac
6jGa7UJWCJA0VemInPIR0J5wlOpDq+GtjKTBaGltAbgVew7U91uuCyB9ll9Ybrug
buETKMaB/o+P57e3atUoWRz5/pUAaZJDE75HDguKS+z2Io5SXR7zOynOhqso89em
kTZ5UvpuO8ffeqqTn9WK7y8roGcYP+PBDdmBgbZF3RysFw+sLaWaRP08rPHMPe7X
Yiw0pZbxSAEwlBcPiPrueqjHxiC1jtGFfpFqaywrNfAkDKSWl/ckzenAZzRlwimS
G0cpbLxGPnvQaqf58jvkntd102tGSMgb7mhVTNDsCu0+IFRfuN+iFy76LpgMwcYc
dZUL5r23gj5Vqe5f9k9GdI8sF6XLPf7juoUXJKRIer9wLhNvTeriv0jCnWhk7SqQ
ysHmtssDzV6jAF9fsGGWrtYTD/LE9NY+WTSDAMv+hZTn/OQZRUPGZ4XS3UN1HE1P
1OWrGlm0IGcgZFzqPRTA
=JW/W
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org