Bug1
出现的异常:
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
严重: The web application [/jiehunn] 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.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [C3P0PooledConnectionPoolManager-Helper Thread-#0] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [C3P0PooledConnectionPoolManager-Helper Thread-#1] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [C3P0PooledConnectionPoolManager-Helper Thread-#2] but has failed to stop it. This is very likely to create a memory leak.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] 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.
2011-11-29 23:57:06 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
严重: The web application [/jiehunn] appears to have started a thread named [AWT-Windows] but has failed to stop it. This is very likely to create a memory leak.
解决方案:
//如果你链接了数据库,更改servlet数据后,不停止tomcat就进行manager Deployments 就会不停的抛这样的严重警告
解决方法;关闭tomcat,然后在开启,然后再运行manager Deployments 下的redeploy,就ok了
Bug2
出现的异常:
MySQL Error Message: Can not connect to MySQL server SQL: Error: Too many connections Errno.: 1040 Click here to seek help. 连接数超过了 MySQL 设置的值,与 max_connections 和 wait_time
连接风信网官网 http://www.ithov.com 突然出现如下错误:
MySQL Error
Message: Can not connect to MySQL server
SQL:
Error: Too many connections
Errno.: 1040
Click here to seek help.
连接数超过了 MySQL 设置的值,与 max_connections 和 wait_timeout 都有关系。wait_timeout 的值越大,连接的空闲等待就越长,这样就会造成当前连接数越大。
解决方法:
1、虚拟主机用户请联系空间商优化 MySQL 服务器的配置;
2、独立主机用户请联系服务器管理员优化 MySQL 服务器的配置,可参考:
修改 MySQL 配置文件(Windows下为 my.ini, Linux下为 my.cnf )中的参数:
max_connections= 1000
wait_timeout = 5
如果没有可以自行添加,修改后重启 MySQL ,如果经常性的报此错误,请做一下服务器的整体优化。
TAG标签: MySQL 错误 Too many connections Errno
Bug3
出现的异常:
java.lang.NullPointerException
cn.csdn.servlet.PlanServlet.doPost(PlanServlet.java:48)
cn.csdn.servlet.PlanServlet.doGet(PlanServlet.java:26)
javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
cn.hbsi.web.filter.CharSetEncodingFilter.doFilter(CharSetEncodingFilter.java:36)
这是因为plandelete.jsp在调用PanServlet.java时没有返回参数,Servlet中获取不到。