tomcat的两个错误提示
来源:互联网 发布:战斗机 知乎 编辑:程序博客网 时间:2024/06/05 14:57
今天tomcat 6遇到两个错误提示:
1.
严重: A web application registered the JBDC 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.
原因:重复加载了jar包。
解决方法:原来我在tomcat的lib文件夹放入了com.mysql.jdbc.Driver的jar包,而又在项目里面重复添加了,导致了上面的提示。删掉其中一个解决问题。
2.The web application [/snoopy] created a ThreadLocal with key of type [com.opensymphony.xwork2.inject.ContainerImpl$10] (value [com.opensymphony.xwork2.inject.ContainerImpl$10@ea85b4]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@efeff8]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
原因:tomcat 6.026之后的版本加入了 memory leak detection feature(内存泄露检查)看如下原文:
There is a memory leak detection feature introduced in Tomcat 6.0.26 that attempts to log objects that have failed to be unregistered by webapps it hosts when they are stopped, and were forcibly unregistered by Tomcat. As Tomcat is forcibly removing these objects, it is not a serious concern that these log messages occur.
解决方法:在tomcat 的server.xml文件中将<!-- <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/> -->注释掉即可
PS:这是一个治标不治本的方法。
1.
严重: A web application registered the JBDC 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.
原因:重复加载了jar包。
解决方法:原来我在tomcat的lib文件夹放入了com.mysql.jdbc.Driver的jar包,而又在项目里面重复添加了,导致了上面的提示。删掉其中一个解决问题。
2.The web application [/snoopy] created a ThreadLocal with key of type [com.opensymphony.xwork2.inject.ContainerImpl$10] (value [com.opensymphony.xwork2.inject.ContainerImpl$10@ea85b4]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@efeff8]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
原因:tomcat 6.026之后的版本加入了 memory leak detection feature(内存泄露检查)看如下原文:
There is a memory leak detection feature introduced in Tomcat 6.0.26 that attempts to log objects that have failed to be unregistered by webapps it hosts when they are stopped, and were forcibly unregistered by Tomcat. As Tomcat is forcibly removing these objects, it is not a serious concern that these log messages occur.
解决方法:在tomcat 的server.xml文件中将<!-- <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/> -->注释掉即可
PS:这是一个治标不治本的方法。
- tomcat的两个错误提示
- phpmyadmin 两个错误提示
- ios开发两个简单的错误提示和原因
- tomcat连接池提示错误
- Tomcat部署提示错误解决方法
- 运行两个tomcat遇到的错误及解决办法
- tomcat+dreamweaver中提示找不到页面的错误
- 在myeclipse 8.6启动tomcat 6x的错误提示
- Tomcat启动后打开页面提示404错误的解决
- tomcat的版本跟换后错误提示:target runtime apache Tomcat v7.0 not defined
- Eclipse同时启用两个tomcat,端口号已经修改,依然提示被占用的解决办法
- Tomcat的两个小东西
- 启动两个tomcat工程 出现错误
- tomcat同时部署两个项目错误
- 在eclipse中启动tomcat提示错误
- Tomcat在eclipse里打不开,提示socket错误
- 在eclipse中启动tomcat提示错误
- “无法播放视频。很抱歉,无法播放此视频” 错误提示的两个原因
- 内存永久保存区域异常 tomcat 、eclipse 参数设置
- Linux文件系统简介
- VS2008无法启动asp.net提示“无法启动程序: http://localhost/.../Login.aspx
- 实例iPhone编程入门教程-第十三天
- Android 应用共用的HttpClient实例实践
- tomcat的两个错误提示
- DNS系统登陆功能测试用例
- Struts2 一个Action实现多个业务逻辑
- 利用ContentProvider和ContentResolver达到QQ换肤以及数据共享查询(暂无内容)
- JAVA读取XML练习,JAVA读取XML文档,JAVA解析XML文档,JAVA与XML,XML文档解析,SAX (Simple API for XML)
- 混色 牛
- gdb+gdbserver远程串行协议
- 混色 牛 2
- .c和.h文件的区别(头文件与之实现文件的的关系~ )