we are using modcluster 1.2.0.Final together with jboss-eap-6.0.1. When we use IPv4, everything is fine.
But when we switch everything to IPv6(including Jboss EAP instances and modcluster itself which means AJP is listening on IPv6 addr and modcluster manager port 6666 is also listening on IPv6 addr and modcluster external incoming traffic is listening on IPv6 addr too). We start getting errors in the modcluster error.log. Just wondering if this is a known issue for modcluster 1.2.0 Final? or I miss configured anything. If it is a known issue, is there any workaround for this issue. thanks a lot,
Here is the mocluster error.log. Is this a bug in modcluster that it cannot parse the ipv6 address?
[Wed May 15 16:20:35 2013] [error] [client (null)] proxy: URI cannot be parsed: ajp://fd00:0:0:0:0:0:0:4%8:30300/ returned by /
[Wed May 15 16:20:37 2013] [error] [client fd00::3] proxy: URI cannot be parsed: ajp://fd00:0:0:0:0:0:0:3%9:30301/ returned by /
[Wed May 15 16:20:37 2013] [error] [client fd00::3] proxy: URI cannot be parsed: ajp://fd00:0:0:0:0:0:0:3%9:30300/ returned by /
Here is the modcluster configuration we used on jboss EAP side.
<mod-cluster-config advertise-socket="modcluster" proxy-list="[fd00::1]:6666" connector="ajp">
In the modcluster manager page, we can see the jboss eap instance is connected. it shows the context as well.
Auto Refresh show DUMP output show INFO output
Node d9f007d6-cd97-3720-99c4-959083f4e2c3 (ajp://[fd00:0:0:0:0:0:0:3%9]:30301):
Enable Contexts Disable Contexts
Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: NOTOK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: -1
Virtual Host 1:
/Example, Status: ENABLED Request: 0 Disable
/FilterExample, Status: ENABLED Request: 0 Disable
/ValveExample, Status: ENABLED Request: 0 Disable
when we actually access the servlet URL, we got 503 "Service Temporarily Unavailable".
"The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
It seems the jboss EAP does send the ajp package to the modcluster. but the modcluster cannot parse the IPv6 URI. "proxy: URI cannot be parsed: ajp://fd00:0:0:0:0:0:0:4%8:30300/"
I also attached the tcpdump for the ajp traffic between JBOSS EAP and Modcluster. from the decoded packets. we can see that JBOSS EAP sends the AJP message to Modcluster, then modcluster response with 200 OK but with the content NOTOK.
HTTP/1.1 200 OK
Date: Wed, 15 May 2013 20:27:47 GMT
Server: Apache/2.2.21 (Unix) mod_cluster/1.2.0.Final mod_ssl/2.2.21 OpenSSL/0.9.8r DAV/2 mod_jk/1.2.30
tcpdump.cap.zip 1.1 KB