Christoph, On 2/22/16 10:56 AM, Christoph P.U. Kukulies wrote: > Being at the problem again since I would like to run haproxy against > tomcat7. > > Here are my connectors: > <Connector port="8080" maxHttpHeaderSize="8192" protocol="HTTP/1.1" > proxyName="test.mydomain.org" maxThreads="150" enableLookups="false" > redirectPort="8443" acceptCount="100" connectionTimeout="20000" > disableUploadTimeout="true" address="0.0.0.0" /> > <Connector port="8081" maxHttpHeaderSize="8192" protocol="HTTP/1.1" > proxyName="www.foobar.de" maxThreads="150" enableLookups="false" > redirectPort="8443" acceptCount="100" connectionTimeout="20000" > disableUploadTimeout="true" address="0.0.0.0" /> > <Connector port="8082" maxHttpHeaderSize="8192" protocol="HTTP/1.1" > proxyName="www.mydomain.org" maxThreads="150" enableLookups="false" > redirectPort="8443" acceptCount="100" connectionTimeout="20000" > disableUploadTimeout="true" address="0.0.0.0" /> > <Connector port="8083" maxHttpHeaderSize="8192" protocol="HTTP/1.1" > proxyName="www.other.org" maxThreads="150" enableLookups="false" > redirectPort="8443" acceptCount="100" connectionTimeout="20000" > disableUploadTimeout="true" address="0.0.0.0" /> > <Connector port="8085" maxHttpHeaderSize="8192" protocol="HTTP/1.1" > proxyName="www.foobaz.de" maxThreads="150" enableLookups="false" > redirectPort="8443" acceptCount="100" connectionTimeout="20000" > disableUploadTimeout="true" address="0.0.0.0" /> > <Connector port="8086" maxHttpHeaderSize="8192" protocol="HTTP/1.1" > proxyName="msg.foobaz.org" maxThreads="150" enableLookups="false" > redirectPort="8443" acceptCount="100" connectionTimeout="20000" > disableUploadTimeout="true" address="0.0.0.0" /> > > > I added the address entry on each connector to no avail: > > # netstat -an > Active Internet connections (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:36762 0.0.0.0:* LISTEN > tcp 0 0 127.0.0.1:60000 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN > tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN > tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN > tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:48397 0.0.0.0:* LISTEN > tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:53264 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:41584 0.0.0.0:* LISTEN > tcp 0 0 0.0.0.0:38836 0.0.0.0:* LISTEN > tcp 0 0 127.0.0.1:3306 127.0.0.1:39401 ESTABLISHED > tcp 0 0 79.80.81.82:993 73.74.75.76:4849 ESTABLISHED > tcp 0 0 79.80.81.82:993 73.74.75.76:4867 ESTABLISHED > tcp 0 0 79.80.81.82:22 73.74.75.76:4491 ESTABLISHED > tcp 0 0 79.80.81.82:993 73.74.75.76:4870 ESTABLISHED > tcp 0 0 79.80.81.82:993 73.74.75.76:4854 ESTABLISHED > tcp 0 0 79.80.81.82:993 73.74.75.76:4873 ESTABLISHED > tcp 0 0 79.80.81.82:993 73.74.75.76:4869 ESTABLISHED > tcp 0 0 79.80.81.82:993 73.74.75.76:4868 ESTABLISHED > tcp6 0 0 :::8085 :::* LISTEN > tcp6 0 0 :::8086 :::* LISTEN > tcp6 0 0 :::22 :::* LISTEN > tcp6 0 0 :::25 :::* LISTEN > tcp6 0 0 :::44001 :::* LISTEN > tcp6 0 0 :::2049 :::* LISTEN > tcp6 0 0 :::993 :::* LISTEN > tcp6 0 0 127.0.0.1:8005 :::* LISTEN > tcp6 0 0 :::42696 :::* LISTEN > tcp6 0 0 :::59018 :::* LISTEN > tcp6 0 0 :::587 :::* LISTEN > tcp6 0 0 :::57999 :::* LISTEN > tcp6 0 0 :::143 :::* LISTEN > tcp6 0 0 :::111 :::* LISTEN > tcp6 0 0 :::8080 :::* LISTEN > tcp6 0 0 :::8081 :::* LISTEN > tcp6 0 0 :::8082 :::* LISTEN > tcp6 0 0 :::8083 :::* LISTEN > tcp6 0 0 :::51795 :::* LISTEN > tcp6 0 0 127.0.0.1:39401 127.0.0.1:3306 ESTABLISHED
Double-check that your configuration is actually being used. Setting address="0.0.0.0" is *supposed* to tie you to the IPv4 address. Note that most Linux TCP/IP stacks use :: to actually listen for both IPv4 and IPv6 connections. Are you mostly looking at the netstat output, or are you finding that IPv4-only clients cannot connect? If address="0.0.0.0" isn't working, you can always set this global JVM parameter to force the use of IPv4. Note that you'll not be able to use IPv6 at that point: -Djava.net.preferIPv4Stack=true -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
