【Tomcat】严重: Context [/grouponAdminWeb] startup failed due to previous errors

1 tomcat 6600启动报错
[[email protected] webapps]#     sh /usr/local/apache-tomcat-6.0.37_6600/bin/startup.sh 
Using CATALINA_BASE:   /usr/local/apache-tomcat-6.0.37_6600
Using CATALINA_HOME:   /usr/local/apache-tomcat-6.0.37_6600
Using CATALINA_TMPDIR: /usr/local/apache-tomcat-6.0.37_6600/temp
Using JRE_HOME:        /usr/java/jdk1.6.0_45
Using CLASSPATH:       /usr/local/apache-tomcat-6.0.37_6600/bin/bootstrap.jar
Using CATALINA_PID:    /var/tomcat/6600.pid
Existing PID file found during start.
Removing/clearing stale PID file.
看到/var/tomcat/6600.pid已经存在了,所以加载失败。停止tomcat,然后检查tomcat进程

2 删除已经存在的6600.pid文件
[[email protected] webapps]# ps -eaf|grep 6600
root     10446  4972  0 15:09 pts/2    00:00:00 grep 6600
[[email protected] webapps]# more /var/tomcat/6600.pid
10180
[[email protected] webapps]# 
[[email protected] webapps]# ll /var/tomcat/6600.pid
-rw-r--r-- 1 root root 6 05-03 15:07 /var/tomcat/6600.pid

[[email protected] webapps]# rm -rf /var/tomcat/6600.pid
[[email protected] webapps]#

3 再重启,还是报错,查看错误日志如下:
tail -n 1000 /usr/local/apache-tomcat-6.0.37_6600/logs/catalina.out
2014-5-3 15:18:29 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/grouponAdminWeb] appears to have started a thread named [Thread-197] but has failed to stop it. This is very likely to create a memory leak.
2014-5-3 15:18:29 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/grouponAdminWeb] appears to have started a thread named [Thread-198] but has failed to stop it. This is very likely to create a memory leak.
......
2014-5-3 15:15:41 org.apache.catalina.startup.HostConfig deployWAR
信息: Deploying web application archive grouponAdminWeb.war
SLF4J: This version of SLF4J requires log4j version 1.2.12 or later. See also http://www.slf4j.org/codes.html#log4j_version
2014-5-3 15:15:44 org.apache.catalina.core.StandardContext start
严重: Error listenerStart
2014-5-3 15:15:44 org.apache.catalina.core.StandardContext start
严重: Context [/grouponAdminWeb] startup failed due to previous errors

从这里可以看出grouponAdminWeb这个web应用在tomcat容器上面deploy失败,为什么失败?

4 分析为什么会deploy应用失败?
找这个应用的设计人员,经过同事提醒,去看同一目录的localhost.2014-05-03.log文件
tail -n 1000 /usr/local/apache-tomcat-6.0.37_6600/logs/localhost.2014-05-03.log
有如下错误提示:
2014-5-3 15:15:41 org.apache.catalina.core.StandardContext listenerStart
严重: Exception sending context initialized event to listener instance of class org.springframework.web.util.Log4jConfigListener
java.lang.IllegalStateException: Web app root system property already set to different value: ‘GrouponWeb.root‘ = [/usr/local/apache-tomcat-6.0.37_6600/webapps/grouponWeb/] instead of [/usr/local/apache-tomcat-6.0.37_6600/webapps/grouponAdminWeb/] - Choose unique values for the ‘webAppRootKey‘ context-param in your web.xml files!
at org.springframework.web.util.WebUtils.setWebAppRootSystemProperty(WebUtils.java:148)
at org.springframework.web.util.Log4jWebConfigurer.initLogging(Log4jWebConfigurer.java:117)
at org.springframework.web.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
at org.apache.catalina.core.StandardService.start(StandardService.java:525)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
2014-5-3 15:15:41 org.apache.catalina.core.ApplicationContext log
信息: Initializing Spring root WebApplicationContext

5  看到错误信息,是配置文件有误,去修改WEB-INF下的web.xml
vim  /usr/local/apache-tomcat-6.0.37_6600/webapps/grouponAdminWeb/WEB-INF/web.xml
将 GrouponWeb.root 的key值由GrouponWeb修改成GrouponAdminWeb,如下所示:

......
<context-param>
        <param-name>webAppRootKey</param-name>
        <param-value>GrouponAdminWeb.root</param-value>
    </context-param>
......

之后重启tomcat或者,重新加载GrouponAdminWeb应用,就OK了。

6 查看最新tomcat启动日志如下
[[email protected] WEB-INF]# tail -n 200 /usr/local/apache-tomcat-6.0.37_6600/logs/catalina.out
信息: Initializing Coyote HTTP/1.1 on http-6600
2014-5-3 15:18:53 org.apache.catalina.startup.Catalina load
信息: Initialization processed in 472 ms
2014-5-3 15:18:53 org.apache.catalina.core.StandardService start
信息: Starting service Catalina
2014-5-3 15:18:53 org.apache.catalina.core.StandardEngine start
信息: Starting Servlet Engine: Apache Tomcat/6.0.37
2014-5-3 15:18:53 org.apache.catalina.startup.HostConfig deployDescriptor
信息: Deploying configuration descriptor manager.xml
2014-5-3 15:18:53 org.apache.catalina.startup.HostConfig deployWAR
信息: Deploying web application archive grouponWeb.war
SLF4J: This version of SLF4J requires log4j version 1.2.12 or later. See also http://www.slf4j.org/codes.html#log4j_version
============
2014-5-3 15:18:58 org.apache.catalina.startup.HostConfig deployWAR
信息: Deploying web application archive grouponAdminWeb.war
SLF4J: This version of SLF4J requires log4j version 1.2.12 or later. See also http://www.slf4j.org/codes.html#log4j_version
============
2014-5-3 15:19:02 org.apache.catalina.startup.HostConfig deployWAR
信息: Deploying web application archive grouponService.war
2014-5-3 15:19:04 org.apache.catalina.startup.HostConfig deployDirectory
信息: Deploying web application directory ROOT
2014-5-3 15:19:04 org.apache.coyote.http11.Http11Protocol start
信息: Starting Coyote HTTP/1.1 on http-6600
2014-5-3 15:19:04 org.apache.jk.common.ChannelSocket init
信息: JK: ajp13 listening on /0.0.0.0:6609
2014-5-3 15:19:04 org.apache.jk.server.JkMain start
信息: Jk running ID=0 time=0/13  config=null
2014-5-3 15:19:04 org.apache.catalina.startup.Catalina start
信息: Server startup in 10955 ms

总结:tomcat容器的web应用加载报错,除了要去看catalina.log日志之外,还要去看localhost.2014-05-03.log日志信息。

【Tomcat】严重: Context [/grouponAdminWeb] startup failed due to previous errors,布布扣,bubuko.com

时间: 2024-10-03 23:23:03

【Tomcat】严重: Context [/grouponAdminWeb] startup failed due to previous errors的相关文章

TOMCAT 显示 Context [/zhgsServer] startup failed due to previous errors

查看细节的错误提示: 23-Feb-2017 09:50:41.179 信息 [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath 23-Feb-2017 09:50:41.210 信息 [localhost-startStop-1] org.apache.catalina.cor

tomcat bug之部署应用的时候经常会发上startup failed due to previous errors

在tomcat上部署应用的时候经常会发上startup failed due to previous errors错误.这个错误产生以后经常会让人摸不到头脑.以下是几点查找经验: 1.web.xml文件,这个文件中定义了很多web服务启动需要的类.xml文件,如果这些找不到就会发生startup failed due to previous errors错误. 2.如果使用spring的话,在applicationContext.xml中定义的类.xml文件找不到也会报这个错误. 3.如果使用i

Context []startup failed due to previous errors 问题解决

log4j.rootLogger=info,Console,R log4j.appender.Console=org.apache.log4j.ConsoleAppender log4j.appender.Console.layout=org.apache.log4j.PatternLayout #log4j.appender.Console.layout.ConversionPattern=%d [%t] %-5p %c - %m%n log4j.appender.Console.layout

org.apache.catalina.core.StandardContext.startInternal Context [/test] startup failed due to previou

解决方法: WEB-INF/classes目录下新建一个文件叫logging.properties,截图如下: 代码如下: 1 handlers=org.apache.juli.FileHandler,java.util.logging.ConsoleHandler 2 ############################################################ 3 #Handler specific properties. 4 # Describes specifi

Linux常见问题解答--如何修复“tar:Exiting with failure status due to previous errors”

问题: 当我用tar命令来创建一个压缩文件时,总在执行过程中失败,并且抛出一个错误说明"tar:由于前一个错误导致失败退出"("Exiting with failure status due to previous errors"). 什么导致这个错误的发生,要如何解决? 当你执行tar命令时,遇到了下面的错误,那么最有可能的原因是对于你想用tar命令压缩的某个文件中,你并不具备其读权限. tar:Exitingwith failure status due to

tar: This does not look like a tar archive tar: Skipping to next header tar: Exiting with failure status due to previous errors

解压一个.tar.zip文件时报错 tar -zxvf bcl2fastq2-v2-20-0-linux-x86-64.zip tar: This does not look like a tar archive tar: Skipping to next header tar: Exiting with failure status due to previous errors 解决办法: unzip bcl2fastq2-v2-20-0-tar.zip 生成 bcl2fastq2-v2.20

linux文件系统解压 tar: Exiting with failure status due to previous errors [Solved]

在执行 $ tar jxf rootfs.tar.bz2 -C ./rootfs/ 时遇到如下问题: tar: dev/console: Cannot mknod: Operation not permitted tar: dev/tty: Cannot mknod: Operation not permitted tar: dev/null: Cannot mknod: Operation not permitted tar: Exiting with failure status due t

windows下启动redis提示Invalid argument during startup: Failed to open the .conf file: redis.windows.connf CWD=C:\Users\Administrator

环境:Windows 7 64bit 旗舰版 redis 3.2.100 64bit 开始的时候,redis运行的好好的,不过每次启动都要要进入其路径,挺麻烦的,所以就想把它的路径设置到环境变量里,然后直接运行就出现错误:Invalid argument during startup:Failed to open the .conf file: redis.windows.connf CWD=C:\Users\Administrator 网上搜索了好久也找不到解决办法.后来想是不是因为环境变量的

Tomcat中Context的配置

Tomcat直接ip地址访问不用加端口和项目名 当我们开发完一个WEB项目 然后部署到tomcat下,正常情况下应该是这样访问:http://localhost:端口号/项目名 如果我们想让用户仅仅输入域名来访问我们的项目,我们就需要修改Tomcat的Context设置. 修改{TOMCAT_HOME}/conf/server.xml文件 使用文本编辑器打开server.xml文件,在<Host>节点下增加<Context>节点,并设置path.docBase.reloadable