Hide Forgot
Created attachment 488474 [details] /etc/tomcat5/Catalina/localhost/rhn.xml
Created attachment 488476 [details] catalina.out during tomcat5 start
RHN Satellite 5.4 is shipped with tomcat5. All the customers that upgrade to tomcat5-5.5.23-0jpp.16.el5 or tomcat5-5.5.23-0jpp.17.el5_6 see attached error in catalina.out. tomcat5-5.5.23-0jpp.11.el5_5 didn't show the error with the same configuration. I attached also the deployed rhn.xml. If any other information/reproducer machine needed, please, contact me.
Just a note: BZ#623465 didn't resolve the issue BZ#678439 might be related
This issue makes tomcat quite unusable if the deployed application puts it's context.xml in /etc/tomcat5/Catalina/localhost -- which is a standard approach to package Tomcat applications as RPM. It may not affect the satellite, but all of our deployments are broken right now.
I've replicated this in tomcat5-5.5.23-0jpp.19.el5. If the context.xml is deployed with the app in META-INF/ without a <appname>.xml in Catalina/localhost, tomcat5 starts without exceptions. The problem doesn't occur when admin and manager apps are deployed. The NPE occurs once the context.xml is in Catalina/localhost. Even though there's a NPE, the webapps still respond and context metadata, such as a Resource, is being honored. I'm looking from 5.5.23-0jpp.11 forward to jpp.16 to find where this was introduced.
reproduced on tomcat5-5.5.23-0jpp.16.el5: https://beaker.engineering.redhat.com/jobs/187858 VERIFIED on tomcat5-5.5.23-0jpp.22.el5_7 https://beaker.engineering.redhat.com/jobs/187885
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0014.html