All,
On 5/24/12 12:09 PM, Christopher Schultz wrote:
> I've recently seen two questions on the users' list and a bunch of
> questions over on StackExchange/ServerFault about mod_jk trying to
> connect to 0.0.0.0 instead of some sane IP address. Many have comments
> saying th
On 05/24/2012 06:09 PM, Christopher Schultz wrote:
All,
I wonder if anyone can remember some similar change that may, in certain
cases, blank-out the server's IP address for mod_jk's workers.
The only thing that can cause that could be shared memory
which has been heavily changed. If worker s
Konstantin,
On 5/24/12 12:14 PM, Konstantin Kolinko wrote:
> 2012/5/24 Christopher Schultz :
>>
>> There also might be something weird with the lookup of "localhost": on
>> one of the SE questions, the OP did "nslookup localhost" and the request
>> went to a DNS server (which returned NXDOMAIN) an
2012/5/24 Christopher Schultz :
>
> There also might be something weird with the lookup of "localhost": on
> one of the SE questions, the OP did "nslookup localhost" and the request
> went to a DNS server (which returned NXDOMAIN) and didn't just
> immediately get 127.0.0.1 from his machine's looku
All,
I've recently seen two questions on the users' list and a bunch of
questions over on StackExchange/ServerFault about mod_jk trying to
connect to 0.0.0.0 instead of some sane IP address. Many have comments
saying that reverting to mod_jk 1.2.35 seems to fix the issue.
I saw t
