Hello, Just load ajp module at least one. No matter if it appears in several file. Apache raised some warning. I didn't see side effect on tomcat or apache if it's loaded several time. Be sure to set it up only once per vhost.
My experience is, my apache servers have mostly standard conf setup by package Installers, and then I load (again) additionnal every vhost loads its modules (php, amp, proxy, ldap...). These configuration are stored in a central versioning system and installed at deployment time. Then I can deploy apps regardless of apache initial setup and operating system (works also on windows too). Regards Stephane Envoyé par BlueMail<http://www.bluemail.me/r?b=14395> Le 12 févr. 2019, à 22:28, "Propes, Barry L " <barry.l.pro...@citi.com.invalid<mailto:barry.l.pro...@citi.com.invalid>> a écrit: Hi folks, First I apologize if this seems more like an Apache question rather than a Tomcat question. I just got an upgraded Red Hat Linux build from 6 to 7, and Apache went from 2.2.15 to 2.4.6. In my older Red hat 6 build, I've got a tomcat.conf file that handles ProxyPass and ProxyPassReverse attributes. I see something similar in the conf.d directory on the Red Hat 7 Apache build, with a file called "proxy_ajp.conf." It comes with some ProxyPass lines commented out by default. I was just wondering if I still need a tomcat.conf file in the new build or if this handles this? I looked for some similar messages and threads but couldn't discern. Again, apologies if this was not the right forum. If this is correct, affirmation of such would be great! Thank you! Barry Propes Citimortgage
