3349 [localhost-startStop-1] INFO org.hibernate.cfg.SettingsFactory - Named query checking : enabled
3349 [localhost-startStop-1] INFO org.hibernate.cfg.SettingsFactory - Check Nullability in Core (should be disabled when Bean Validation is on): enabled
4049 [localhost-startStop-1] INFO org.quartz.core.QuartzScheduler - Scheduler scheduler_$_NON_CLUSTERED shutting down.
4049 [localhost-startStop-1] INFO org.quartz.core.QuartzScheduler - Scheduler scheduler_$_NON_CLUSTERED paused.
4053 [localhost-startStop-1] INFO org.quartz.core.QuartzScheduler - Scheduler scheduler_$_NON_CLUSTERED shutdown complete.
Mar 02, 2016 4:01:45 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
Mar 02, 2016 4:01:45 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/heximobile] startup failed due to previous errors
Mar 02, 2016 4:01:45 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc
SEVERE: The web application [/heximobile] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Mar 02, 2016 4:01:45 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/heximobile] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.
Mar 02, 2016 4:01:45 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/heximobile] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
Mar 02, 2016 4:01:45 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /usr/apache-tomcat-7.0.67/webapps/heximobile has finished in 50,024 ms
Mar 02, 2016 4:01:45 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-1303"]
Mar 02, 2016 4:01:45 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Mar 02, 2016 4:01:45 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 50731 ms
tomcat 启动报错 startup failed due to previous errors
- 写回答
- 好问题 0 提建议
- 追加酬金
- 关注问题
- 邀请回答
-
4条回答 默认 最新
- usernameaaaa 2016-03-02 09:16关注
1.web.xml文件,这个文件中定义了很多web服务启动需要的类、xml文件,如果这些找不到就会发生startup failed due to previous errors错误。
2.如果使用spring的话,在applicationContext.xml中定义的类、xml文件找不到也会报这个错误。
3。如果使用ibatis的话,在SqlMapConfig.xml中定义的xml文件找不到也会报这个错误。
总结的经验就是一定要把配置文件中定义的每条信息弄清楚,不要拿来别人的代码就使用,这样就会解决这个问题。解决 2无用
悬赏问题
- ¥15 数学建模招标中位数问题
- ¥15 phython路径名过长报错 不知道什么问题
- ¥15 深度学习中模型转换该怎么实现
- ¥15 HLs设计手写数字识别程序编译通不过
- ¥15 Stata外部命令安装问题求帮助!
- ¥15 从键盘随机输入A-H中的一串字符串,用七段数码管方法进行绘制。提交代码及运行截图。
- ¥15 TYPCE母转母,插入认方向
- ¥15 如何用python向钉钉机器人发送可以放大的图片?
- ¥15 matlab(相关搜索:紧聚焦)
- ¥15 基于51单片机的厨房煤气泄露检测报警系统设计