Hi Chris, Post the Ghostcat changes tomcat now listens only on ipv4 by default, what if somebody is using on IPv6, Tomcat starts to listen on mapped IPv4 address which I think is not correct. I know that we can use ::1 in IPv6. Is there a way tomcat can listen on both loopback addresses when available.
Thank you, Kishore -----Original Message----- From: Christopher Schultz <ch...@christopherschultz.net> Sent: Tuesday, April 28, 2020 8:19 PM To: users@tomcat.apache.org Subject: Re: Issue with AJP listener -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Satya, On 4/28/20 06:06, Satya Kishore Thumu wrote: > We are using apache before Tomcat as front end and using modjk for > connection between apache and Tomcat. After upgrading tomcat(to > 7.0.100 as we have other dependencies we can't use latest as of now), > i'm unable to use ajp.host as "localhost" in IPv6 and works only with > ::1. Need help if there is any configuration that can be done to use > localhost even in IPv6 environment. The issue is that Tomcat changed its default "address" from "all interfaces" to "localhost". This change was made in Tomcat 7.0.100 in the 7.0.x branch. Apache httpd and Java may disagree as to how "localhost" resolves. If you want to force Tomcat to use the IPv4 address, you should be able to do this in your conf/server.xml: <Connector address="127.0.0.1" ... /> Then restart Tomcat. This will cause Tomcat to bind to the IPv4 flavor of "localhost" and httpd should be abel to communicate again. Note that there were other changes related to AJP connections in the same version. Please read this carefully: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html#Tomcat_7.0.100_(v ioletagg) Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl6oQlAACgkQHPApP6U8 pFiwuw//dlNNPtsCM85g8ejOawkY4LCOCJTkXc5q6vO1mbjMkrUd/0AnShdpTDLS 8tQSv6HY/b9pXv02hISK067P3y6zF9GOgoZPHZ/u5WErvAYpQnX77nrytuejhLXI QumMEojR9QTOxhsXXx2cn4Z4EjrQQ3yR4TjJ0yiuLmQDD24NlNww+LtXCidbponv t4hrplShX/OH8X4Il41t0cGM5Rij6qgiI5AnwBpzULJ0wroj/Hnu6w6GSO/xxY4h ToZmnKSN8sPkEs8UQKc0tf6NCZUGXMmbz3XoGgM9sL31uQI8+NuwinYChjBfy2JA /bn+n5uKZ60ut0TLTwYA3nj5C7EhypszZtVYQmAqWtbVo+kHdhE6wqMbuGPdRgui wEBItaAOCBxrMLXZyFGjMVam76AbG/RBNHsBTnogOVbHSl5CrM1jCjB8s/+uLlmB Y/sSbgqvXxYjCBic3G+6++u5QQ4OwzZUuidcjQGpkDNOfqk5Bxl757C+vGrcwnjx vYmRUQHJcHdiVJvzCrSw0OlL7/Q6w5lFE383Fdirs+DMIyj3qprFzHn25ShNAsPN Pe9FqL8E55mNBchxjWEdKgqryS5Po20Tm1vnwK/UDECfsf+/0mpNCCaZpXcLFaco Ex4UCamwEPwGNeeunRIys/8eKKRCoEa8l2VhiB9JkjlqeDWFplY= =pcIq -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
smime.p7s
Description: S/MIME Cryptographic Signature
