#Apache tomcat 7.0.42 update#

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. Make sure basics such as network (/etc/nf) are correct we do not know the details/specifics.Make sure your system has the proper repositories attached including JBoss, Please see Christian Labisch's post.

Make sure your system is properly subscribed.

Make sure your system can either see Red Hat's repositories in the output or your Red Hat satellite we do not know the details/specifics.

# if your system is not subscribed properly, please fix that, we do not know that ~ ] # yum clean ~ ] # yum repolist # The idea here is to check for competing or distracting repo files that might be getting in the way. # note, hopefully you get a realistic output of expected Red Hat repositories, **to include ~ ] # ls /etc//*repo # note, hopefully this says 'Current' for 'Overall Status', if not, register ~ ] # yum repolist

Try these ~ ] # subscription-manager status.

because we don't know your background, or the details/specifics behind this and what has or has not been done.

#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?