Bug 678439

Summary: more NullPointerExceptions from context.xml
Product: Red Hat Enterprise Linux 5 Reporter: Jeff Bastian <jbastian>
Component: tomcat5Assignee: David Knox <dknox>
Status: CLOSED WONTFIX QA Contact: tomcat-qe
Severity: medium Docs Contact:
Priority: high    
Version: 5.6CC: chris.kreutzer, jbastian, jclere, jpazdziora, jpechane, mhasko, schlegel, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: tomcat5-5.5.23-0jpp.20.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-07 19:35:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
catalina.out log none

Description Jeff Bastian 2011-02-17 22:35:48 UTC 
Created attachment 479417 [details]
catalina.out log

Description of problem:
This is a continuation of bug 623465.  In that bug, an empty context.xml would cause a NullPointerException error.  However, I can still get a NullPointerException even with a non-empty context.xml, for example:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<?xml version="1.0" encoding="UTF-8"?>
<Context>
        <ResourceLink name="jdbc/ds_application_qwerty"
                global="ds_qwerty"
                type="javax.sql.DataSource" />
</Context>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Version-Release number of selected component (if applicable):
java-1.6.0-openjdk-1.6.0.0-1.18.b17.el5.i386
java-1.6.0-openjdk-devel-1.6.0.0-1.18.b17.el5.i386
tomcat5-5.5.23-0jpp.16.el5.i386
tomcat5-admin-webapps-5.5.23-0jpp.16.el5.i386
tomcat5-common-lib-5.5.23-0jpp.16.el5.i386
tomcat5-jasper-5.5.23-0jpp.16.el5.i386
tomcat5-jsp-2.0-api-5.5.23-0jpp.16.el5.i386
tomcat5-server-lib-5.5.23-0jpp.16.el5.i386
tomcat5-servlet-2.4-api-5.5.23-0jpp.16.el5.i386
tomcat5-webapps-5.5.23-0jpp.16.el5.i386

How reproducible:
every time

Steps to Reproduce:
1. Install RHEL 5.6 with above java and tomcat5 packages and run
   system-switch-java to ensure OpenJDK is the selected JRE.
2. Create /etc/tomcat5/Catalina/localhost/context.xml with contents
   as shown above
3. tail -f /var/log/tomcat5/catalina.out
   service tomcat5 start
  
Actual results:
Feb 17, 2011 5:32:31 PM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start: 
LifecycleException:  Error initializaing :  java.lang.NullPointerException
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:3986)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
        ...

Expected results:
no NullPointerException

Additional info:
Comment 1 Chris Kreutzer 2011-02-22 22:33:58 UTC 
I am receiving the exact same response from any /etc/tomcat5/Catalina/localhost/<context>.xml .  Even ones that are autogenerated from a deployed war file.

My <context>.xml is very simple :

<?xml version="1.0" encoding="UTF-8"?>
<Context path="/thredds">
</Context>


I am running RHEL5  and tomcat version  5.5.23-0jpp.16.el5
Comment 2 Chris Kreutzer 2011-02-22 22:34:48 UTC 
sorry that was RHEL5.6
Comment 5 Gunther Schlegel 2011-05-23 14:00:12 UTC 
I am seing this with more or less every context.xml.
Comment 6 David Knox 2011-05-23 15:12:45 UTC 
This looks like the same thing as in bug 689924.
Comment 8 RHEL Program Management 2011-06-22 19:37:25 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 9 RHEL Program Management 2011-12-20 18:37:13 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 10 Michal Haško 2012-02-01 13:25:06 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 11 RHEL Program Management 2014-03-07 12:11:55 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in the  last planned RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX. To request that Red Hat re-consider this request, please re-open the bugzilla via  appropriate support channels and provide additional business and/or technical details about its importance to you.