Red Hat Bugzilla – Bug 623465
tomcat5 upgrade to tomcat5 causes exception at start
Last modified: 2015-11-01 19:15:49 EST
Description of problem:
Upgraded to tomcat5-5.5.23-0jpp.9.el5_5, and on restart, the following is logged:
Aug 11, 2010 12:13:54 PM org.apache.catalina.core.ContainerBase
SEVERE: ContainerBase.addChild: start:
LifecycleException: Error initializaing : java.lang.NullPointerException
Version-Release number of selected component (if applicable):
Please see rhbz#623254
cvs tag: tomcat5-5_5_23-0jpp_10_el5_5
Created attachment 438310 [details]
context.xml that triggers problem
I don't think it's the same as the StackOverflow problem, since this is a NullPointerException.
We have tomcat running several applications, and we're only seeing this on ones that use a $THOME/conf/Catalina/localhost/<context>.xml file to set database connection information, etc. I attached a sample (with passwords redacted).
Thanks. Could you also attach a complete log file including the exception, please?
Confirmed. the problem is related to the existence of a $CAT_HOME/conf/Catalina/localhost/context.xml.
Any empty context.xml in that specific location will cause the same problem. The same context.xml in /etc/tomcat5/ will not produce the problem. Changing the context path (path="/foo") also produces the problem.
Same issue here with context tags but in a different file. I'm an RHCE and have worked with 2 other RHCEs at RH ending up with the same result. 32-bit or 64-bit system, using GCJ Java or our requirement for Sun Java 1.6.0.
I have RH case # 2050882 open as well. This problem is not specific to the webapp's context.xml either, if you put in a global context in /usr/share/tomcat5/conf/server.xml, 0.jpp9 and 0.jpp10 will also crash, remove the context tags and tomcat starts up. The crash on startup leaves the ports open, but tomcat is unresponsive on his http port. A ps listing shows tomcat running but it does not respond when you post a "GET /webapplication/ HTTP/1.0" when attempting a connection to port 8080.
Jim Roland, RHCE
FYI, a Context element in server.xml is no longer considered appropriate. The recommendation is to put a <context>.xml in conf (for a default) or in Catalina/<host>/<context>.xml
That said, it doesn't change the issue, which has been narrowed down to a particular place. I don't have an eta yet, but am working on it.
*** Bug 623813 has been marked as a duplicate of this bug. ***
What is the status on fixing this issue?
Are you guys waiting on me to QA this or are you in QA yourselves? Just asking if you need anything from me in the next several days?
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Still has startup issues (http404) on first request. The second request will return http200.See comment 15.
We will continue to track this down.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.