SEVERE: ContainerBase.addChild: start:org.apache.catalina.LifecycleException: Failed to start error

问题:

I encountered this error when I tried to run my application in Tomcat. I already checked the version of tomcat and java home. Both use java 6.

Is there a missing jar? Or is it my web xml? I'm not using any maven tool.

SEVERE: ContainerBase.addChild: start:  org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/ICard]]     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:650)     at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1582)     at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)     at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)     at java.util.concurrent.FutureTask.run(Unknown Source)     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)     at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoClassDefFoundError: javax/xml/rpc/handler/soap/SOAPMessageContext     at java.lang.ClassLoader.defineClass1(Native Method)     at java.lang.ClassLoader.defineClassCond(Unknown Source)     at java.lang.ClassLoader.defineClass(Unknown Source)     at java.security.SecureClassLoader.defineClass(Unknown Source)     at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2904)     at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1173)     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1681)     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)     at java.lang.Class.getDeclaredMethods0(Native Method)     at java.lang.Class.privateGetDeclaredMethods(Unknown Source)     at java.lang.Class.getDeclaredMethods(Unknown Source)     at org.apache.catalina.util.Introspection.getDeclaredMethods(Introspection.java:108)     at org.apache.catalina.startup.WebAnnotationSet.loadMethodsAnnotation(WebAnnotationSet.java:279)     at org.apache.catalina.startup.WebAnnotationSet.loadApplicationServletAnnotations(WebAnnotationSet.java:141)     at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:67)     at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:405)     at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:881)     at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)     at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)     at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)     at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)     ... 11 more Caused by: java.lang.ClassNotFoundException: javax.xml.rpc.handler.soap.SOAPMessageContext     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714)     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)     ... 33 more Jan 10, 2014 4:05:06 PM org.apache.catalina.startup.HostConfig deployDescriptor SEVERE: Error deploying configuration descriptor F:\RCBC\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\conf\Catalina\localhost\ICard.xml java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/ICard]]     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)     at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:650)     at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1582)     at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)     at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)     at java.util.concurrent.FutureTask.run(Unknown Source)     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)     at java.lang.Thread.run(Unknown Source) Jan 10, 2014 4:05:06 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-8100"] Jan 10, 2014 4:05:06 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["ajp-bio-8009"] Jan 10, 2014 4:05:06 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 4003 ms

回答1:

Got the solution for this problem.... Wooo

1. Make sure that Appliction server (Tomcat etc.) uses the same java runtime version as per what your java application is using.

2. Make sure that your using jre path not jdk path for the runtime enviroments

3. Make sure when creating a project select the appropriate server runtime versions.

回答2:

This issue arises because of different reasons. It might encountered if you are using Spring boot built war file. As Spring boot web and rest starter projects jars do have embedded Tomcat in it, hence fails with "SEVERE: ContainerBase.addChild: start: org.apache.catalina.LifecycleException".

You can fix this by exclusion of the embedded tomcat at the time of packaging by using exclusions in case of maven.

Maven dependency of "spring-boot-starter-web" will look like

   org.springframework.bootspring-boot-starter-weborg.springframework.bootspring-boot-starter-tomcat

回答3:

According to me, this would happen if there are two offending classes of same name but with different version. Usually, it happens due to servlet-api.jar. If its present in lib folder of your war, then pls remove it using whichever tool used for building war. Or in case of maven, add the dependency with scope specified as "provided". This will solve the compilation issue and at run time it will refer to jar provided by server environment. Pls configure the dependency as follows:

javax.servletjavax.servlet-api3.0.1provided

回答4:

What caused this error in my case was having two @GET methods with the same path in a single resource. Changing the @Path of one of the methods solved it for me.

回答5:

Main reason：SOAPMessageContext NoClassDefFoundError So you need import this Class or jar

in IDEA

1. ctrl+shift+alt+S，“Libraries”,find the absent class.
2. edit the local Maven config.

.m2/repository/your absent class(for example commons-logging)/.../maven-metadata-central.xml

commons-loggingcommons-logging1.21.21.01.0.11.0.21.0.31.0.41.11.1.11.1.21.1.31.220140709195742your need absend class version and useful

because Maven will find 'metadata-central.xml' config lastest version as project use version.

forgive my chinese english:)

回答6:

Please verify your .project and .classpath files. Verify the java version and other reuqired details. If those and missing or mis matched

回答7:

I'm not sure what happened in your case that fixed the issue, but your issue was on this line:

Caused by: java.lang.NoClassDefFoundError: javax/xml/rpc/handler/soap/SOAPMessageContext

You need to add jaxrpc-api.jar to your /libs or add

javax.xmljaxrpc-apix.x.x

to your maven dependencies.

回答8:

I had the same error statement following a "Failed to access resource" error message:

Command

#cat callflow-java-logger-1.log.0

Output

Dec 09, 2015 8:09:03 AM org.apache.catalina.loader.WebappLoader startInternal SEVERE: LifecycleException  java.io.IOException: Failed to access resource /WEB-INF/lib/ojdbc14.jar

In my case the solution was changing the connector permissions

-rw------- 1 owner creator size date ojdbc14.jar

This file in question wasn't initially located at /WEB-INF/lib, which was probably due to how BIRT works. It can be tricky if you are dealing with a higher number of files.

回答9:

Weird error, you can try methods given by james goooseling and also I have done it by following ways:

• Remove all jars or libraries from build path and lib folders and add them again in lib folder or build path as you wish.

• Check if you have servlet annotation @WebServlet for given servlet and if it has mapping in web.xml as well .. this is most common error due to which tomcat gets confused , that what url pattern must he use.

回答10:

In my case the servlet name defined in the web.xml was not same as the sevlet name in the servlet mapping tag. I have corrected this and the WAR was deployed successfully.

回答11:

my problem was with @WebServelet annotation and it was because of the name was repeated, I had two of @WebServlet("/route")in my code by mistake(I copy and pasted and forgot to change the route name)

回答12:

My problem was that I had @WebServlet("/route") and the same servlet declared in web.xml

回答13:

In my case (Spring MVC + Hibernate project), I added Controller, Service, Dao, Model class & Thyme leaf page. Just didn't map new model class in "hibernate.cfg.xml" file. So that got this error. But after mapping new model class again got the error. Then deleted Controller, Service, Dao, Model class. Thyme leaf page and Created newly. Also mapped new model class. Then error has gone.

回答14:

On top of all the other stuff, for me this was happening because I was activating NewRelic in my setenv.sh:

NR_JAR=/opt/newrelic/newrelic.jar; export NR_JAR

Once I commented this, removing newrelic's hooks, the issue disappeared. It was only happening for endpoints using apache CXF.

转载请标明出处:SEVERE: ContainerBase.addChild: start:org.apache.catalina.LifecycleException: Failed to start error

文章来源: SEVERE: ContainerBase.addChild: start:org.apache.catalina.LifecycleException: Failed to start error