Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats

[Nelson Lago]

Hi,

I have exactly the same issue as the original poster:

1. Debian 6.0/amd64 running as a guest under OpenVZ
2. Host kernel: 2.6.26-2-openvz-amd64 (the host is debian lenny)
3. The connector is enabled in tomcat
4. Downgrading from 1:1.2.30-1 to 1:1.2.26-2+lenny1 solves the problem
5. Substituting the mod_jk.so file for the binary available from
apache.org also solves the problem

The original poster apparently is also using OpenVZ, so I guess this
is why others were unable to reproduce it. Still, the problem is most
likely in the debian package, as the older version is ok and the
apache binary is also ok. The original poster tested apache's version
1.2.31, but I tested both 1.2.31 and 1.2.30 and they both work ok.

So, this problem has nothing to do with the lack of documentation
about re-enabling ajp13 in tomcat (although this should be addressed
too).

Please note that the error issued is 22: EINVAL. This is not
"connection refused". Tomcat is listening on an ipv6 socket. I can
connect to it using netcat, for instance (which is an ipv4
application), but I still think the problem here has to do with
ipv6/ipv4. If my memory serves me correctly, mod_jk is ipv4 only. I
tried setting the address directive in the tomcat connector to
127.0.0.1 to "force" it to use ipv4, but netstat still lists the
socket as ipv6:

tcp6       0      0 127.0.0.1:8009          :::*
LISTEN      2449/java

I am available to perform tests on this if necessary, this is a "real"
server but is not critical.