
While Red Hat backports fixes and then adds a custom version number, the automated tool does not check to see if a fix is actually implemented. Automated audits only look at version number. There are a couple of things to remember.ġ. Make an sosreport if you submit a case to Red Hat and attach it to the case. Hope this helps, you can submit a ticket since JBoss is a supported product.
#Apache tomcat 7.0.42 update
Maybe a simple yum clean all/yum update in the way you were doing before will sometimes fix issues. You're familiar with backporting? I ask because you mention Based on upstream Tomcat 7 - the upstream non-Red Hat provided tomcat and httpd are cherry-picked by Red Hat and Red Hat produces their own Red Hat rpms based on backporting You may know this already - we do not know the details/specifics of your situation, so we ask.



Can you provide the output of the errors you receive with yum update with RHEL 7?Ī search of the tomcat rpm at shows version tomcat-7.0.76-16.el7_9.noarch.rpm Ī search for the httpd rpm at shows version httpd-2.4.6-97.el7_9.5.x86_64.rpm Īlso, you mention PCI audit which says to update apache - I'm not familiar with JBOSS - is "PCI audit" part of Jboss? Or is it third party?
