Bug 691833

Summary: tomcat5-5.5.23-0jpp.16.el5.x86_64 causes errors when deploying rhn.xml at tomcat5 startup
Product: Red Hat Enterprise Linux 5 Reporter: Tomas Lestach <tlestach>
Component: tomcat5Assignee: David Knox <dknox>
Status: CLOSED ERRATA QA Contact: tomcat-qe
Severity: medium Docs Contact:
Priority: high    
Version: 5.6CC: bgollahe, cperry, cww, fdewaley, jclere, jpazdziora, jwest, lmiksik, mhasko, mosvald, schlegel, syeghiay
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: tomcat5-5.5.23-0jpp.20.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 681503 Environment:
Last Closed: 2013-01-08 07:06:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 681503    
Bug Blocks: 717459    
Attachments:
Description Flags
/etc/tomcat5/Catalina/localhost/rhn.xml
none
catalina.out during tomcat5 start none

Comment 1 Tomas Lestach 2011-03-29 15:23:04 UTC
Created attachment 488474 [details]
/etc/tomcat5/Catalina/localhost/rhn.xml

Comment 2 Tomas Lestach 2011-03-29 15:27:00 UTC
Created attachment 488476 [details]
catalina.out during tomcat5 start

Comment 3 Tomas Lestach 2011-03-29 15:33:37 UTC
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.

Comment 4 Tomas Lestach 2011-03-29 15:51:18 UTC
Just a note:
 BZ#623465 didn't resolve the issue
 BZ#678439 might be related

Comment 6 Gunther Schlegel 2011-05-20 19:11:03 UTC
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.

Comment 8 David Knox 2011-06-21 19:22:01 UTC
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.

Comment 14 Michal Haško 2012-02-01 13:25:04 UTC
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

Comment 19 errata-xmlrpc 2013-01-08 07:06:38 UTC
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