关于org.apache.catalina.LifecycleException解决方案



由于项目需要用到myeclipse,在试用中发现项目可以用myeclipse自带的tomcat正常部署发布,但是使用配置的tomcat7却不能正常试用,报下面的异常:

严重: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/productmanager]]
 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:652)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1263)
 at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1978)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.SecurityException: invalid SHA1 signature file digest for javax/activation/MimeType.class
 at sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:438)
 at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:231)
 at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:176)
 at java.util.jar.JarVerifier.processEntry(JarVerifier.java:277)
 at java.util.jar.JarVerifier.update(JarVerifier.java:188)
 at java.util.jar.JarFile.initializeVerifier(JarFile.java:321)
 at java.util.jar.JarFile.getInputStream(JarFile.java:386)
 at org.apache.catalina.loader.WebappClassLoaderBase.findResourceInternal(WebappClassLoaderBase.java:3327)
 at org.apache.catalina.loader.WebappClassLoaderBase.findResource(WebappClassLoaderBase.java:1426)
 at org.apache.catalina.loader.WebappClassLoaderBase.getResourceAsStream(WebappClassLoaderBase.java:1654)
 at org.apache.catalina.startup.ContextConfig.populateJavaClassCache(ContextConfig.java:2242)
 at org.apache.catalina.startup.ContextConfig.populateJavaClassCache(ContextConfig.java:2232)
 at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2138)
 at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2090)
 at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1965)
 at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1931)
 at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1916)
 at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1330)
 at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:889)
 at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:386)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
 at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
 at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5405)
 at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
 ... 11 more
2016-2-23 14:47:15 org.apache.catalina.startup.HostConfig deployDirectory
严重: Error deploying web application directory D:\Tomcat 7.01\webapps\productmanager
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/productmanager]]
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:905)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
 at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1263)
 at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1978)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:619)
2016-2-23 14:47:15 org.apache.catalina.startup.HostConfig deployDirectory
信息: Deployment of web application directory D:\Tomcat 7.01\webapps\productmanager has finished in 2,040 ms
2016-2-23 14:47:15 org.apache.catalina.startup.HostConfig deployDirectory
信息: Deploying web application directory D:\Tomcat 7.01\webapps\ROOT
2016-2-23 14:47:15 org.apache.catalina.startup.HostConfig deployDirectory
信息: Deployment of web application directory D:\Tomcat 7.01\webapps\ROOT has finished in 78 ms
2016-2-23 14:47:15 org.apache.coyote.AbstractProtocol start
信息: Starting ProtocolHandler ["http-bio-8088"]
2016-2-23 14:47:15 org.apache.coyote.AbstractProtocol start
信息: Starting ProtocolHandler ["ajp-bio-8009"]
2016-2-23 14:47:15 org.apache.catalina.startup.Catalina start
信息: Server startup in 2689 ms


通过查找资料发现网上大部分原因是web.xml配置出现问题,但是检查自己项目可以确定没有问题,并且用myeclipse自带的可以部署成功。


继续探究发现如果将项目打包放入tomcat可以正常发布部署,说明项目和tomcat都没有问题。


通过以上说明问题出现在版本上面,通过myeclipse自带tomcat版本为tomcat6.0,于是将配置的tomcat更换为6.0,测试成功


总结:

1.配置文件书写不规范,解析异常

2.服务器版本不匹配

  • 1
    点赞
  • 3
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值