-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Darryl,

On 5/1/20 14:32, Darryl Philip Baker wrote:
> Continuing the investigation:
>
> I have the two tomcat installation in /opt/tomcat. Apache HTTPD
references the worker file using a path that has a symbolic link that
"latest" I can switch to point to either installation of tomcat. The
workers file is defined in httpd.conf as "JkWorkersFile
/opt/tomcat/latest/conf/jk/workers.properties"
>
> Tomcat 9.0.20 works as expected. Tomcat 9.0.34 fails with just
having the browser clocking and not returning.
>
> Just to give you an idea of the differences in the control files:
>
> [[root@lmsdevsyncapp7 tomcat]# diff
apache-tomcat-9.0.20/conf/server.xml apache-tomcat-9.0.34/conf/server.xm
l
> 79c79 <     <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
> ---
>> <!-- Define an SSL/TLS HTTP/1.1 Connector on port 8443
> 96c96 <     <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
> with HTTP/2 ---
>> <!-- Define an SSL/TLS HTTP/1.1 Connector on port 8443 with
>> HTTP/2
> 115a116,118
>> <!-- address="127.0.0.1" worker.worker1.secret="false" -->
> 119d121 <         address="127.0.0.1" [root@lmsdevsyncapp7 tomcat]#
> diff
apache-tomcat-9.0.20/conf/jk/workers.properties
apache-tomcat-9.0.34/conf/jk/workers.properties
> [root@lmsdevsyncapp7 tomcat]# ls -l total 8 drwxrwxr-x 9 tomcat
> tomcat 4096 May 16  2019 apache-tomcat-9.0.20 drwxr-xr-x 9 tomcat
> tomcat 4096 Apr 28 11:59 apache-tomcat-9.0.34 lrwxrwxrwx 1 root
> root     20 Apr 28 15:00 latest ->
apache-tomcat-9.0.34
> [root@lmsdevsyncapp7 tomcat]#

Something seems fishy.

First, your workers.properties files should not have had to change at
all. Were there any changes made, there?

Second, you have a diff of the server.xml files with virtually no
changes and yet 9.0.20 did NOT have a "secretRequired" attribute
available (it was introduced in 9.0.31). So why does your 9.0.20
installation have secretRequired="false" in it?

Finally, there was another change in 9.0.31 that changed the way the
connector binds to network interfaces. Your old interface specified
"127.0.0.1" (shown in the diff) and the new one does not specify
anything (except, oddly, you quoted that in your original message as
saying it DOES have address="127.0.0.1" so it's really difficult what
is real and what is not real, here. If you aren't specifying an
"address", then you are getting whatever Java finds when it looks-up
"localhost". That will either be an IPv4 or IPv6 interface. We have
seen some problems where httpd and Java come to different conclusions
as to which interface to use. It's best to specify exactly which
interface you want to use *by IP address* and not by hostname. So, if
you want to use IPv4, then use 127.0.0.1 in both places
(workers.properties and server.xml).

Hope that helps,
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl6sj3kACgkQHPApP6U8
pFgPJQ//Su/qv/PEYohk6lzma8kiyAC2+6+zo4LsIxq2yu9SKlz357rIxstFQgfd
Zdsuhs/QHZA8elpGbo3ecMZ4BikAAFHfwmXK4fEUBqSejCcdI2VY7bBumpYPIrYG
zTaOSBfX5UNA+IgWSoQvbtUutnoGIrg+cPSR+eJz/NOl87xiM2fwWaMlZFqGw5Qv
pnEpvtfljQtTiG7TC1KX8Ys91uWoiaF8SLrqW4KGdTQpkBQwMwmUFCpS0UksTnoR
jhUqb+Wxav+sjLpazwiZP0mwCx2liVKAv4TQOOMjSHU16eQRDK81HzpeZytl9A0V
qYIl3d6+d+P6+TSW0z9t1enIp6BMcl05G9g6ONUvxMsRsTaIV5UiT5iKhUP7BRHF
D0CXphFJy+4I8LSNvrjgKt0laneSF0R8JHtH5aRdsQkalJxEr4filQXSdgcwcQ2v
GhtUU5MBe56HPijml+S5v6CZ8C7SG1UhZxeVTS0jxsrQhkCPBFCVseKq5Wfsj6v3
VAJxUBBUm2eL4APBvDB24dpqY3Uiycj2yW89vY/lG93wq8fF8F9pnra4XkAIxa2N
HwQnNO508TAHULGT9fqp7mCMnTHfKeoqtY+6I1wMOV4YS8kI1wsvMtkaBnE4pweS
2dyKGnoqEZCpkK0slXHaJXX+dttVMMKFWl/JQC5pcIvfaVAhLI0=
=J0sn
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to