tomcat分析.docVIP

tomcat连接池的三个重要参数 引用: a.? ?如果设为true则tomcat自动检查恢复重新利用，没有正常关闭的Connection.（默认是false）??parameter??nameremoveAbandoned/name??valuetrue/value??/parameterb.? ?设定连接在多少秒内被认为是放弃的连接，即可进行恢复利用。??parameter??nameremoveAbandonedTimeout/name??value60/value??/parameterc.? ?输出回收的日志，可以详细打印出异常从而发现是在那里发生了泄漏??parameter??namelogAbandoned/name??valuetrue/value??/parameter 实验环境，tomcat配置连接池，最大连接数为5.代码如下： ? parameter????????????????namemaxActive/name????????????????value5/value?????????????????????????/parameter????????????parameter????????????????namemaxIdle/name????????????????value1/value??????????????????????????/parameter????????????parameter????????????????namemaxWait/name????????????????value20000/value??????????????????????/parameter????????????parameter????????????????nameremoveAbandoned/name????????????????valuetrue/value????????????/parameter????????????parameter?????????????????nameremoveAbandonedTimeout/name?????????????????value60/value????????????/parameter????????????parameter?????????????????namelogAbandoned/name?????????????????valuetrue/value????????????/parameter 使用如下代码进行实验（每一次不关闭连接）： try?{????Connection?con?=?getJdbcDAO().getDataSource().getConnection();????ResultSet?rs?=?con.createStatement().executeQuery(select?*?from?K_MS..B_MSPBXX);????while?(rs.next())?{????????System.out.println(rs.getString(1));????}}?catch?(SQLException?e)?{?????e.printStackTrace();} 当该连续执行5次之后，后台就报连接池满的错： 2008-09-06 14:31:02,471 [org.hibernate.util.JDBCExceptionReporter]-[WARN] SQL Error: 0, SQLState: null2008-09-06 14:31:02,471 [org.hibernate.util.JDBCExceptionReporter]-[ERROR] Cannot get a connection, pool exhausted2008-09-06 14:31:02,580 [org.hibernate.util.JDBCExceptionReporter]-[WARN] SQL Error: 0, SQLState: null2008-09-06 14:31:02,580 [org.hibernate.util.JDBCExceptionReporter]-[ERROR] Cannot get a connection, pool exhausted 根据如下脚本查数据库连接 declare?cur_spid?cursor?forselect?spid?from?sysprocesses?where?ipaddr=45?and?program_name??SQL_Adva