MySQLNonTransientConnectionException: No operations allowed after co
2017-11-13 23:07
417 查看
今天在连接数据库的时候遇到这个问题:
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.
一直没办法解决,就到网上看了别人的博客,下面是转载的内容:
分析,出现这种异常的原因是:
Mysql服务器默认的“wait_timeout”是8小时,也就是说一个connection空间超过8个小时,Mysql将自动断开该connection,这就是问题所在,在连接池中的connection如果空闲超过8小时,mysql将其断开,连接池并不知道该connection已失效,如果这时有client请求connection,连接池将失效的connection提供给client,将会造成上面的异常。
解决的方法有3种:
增加wait_timeout的时间。
减少Connection pools中connection的lifetime。
测试Connection pools中connection的有效性。
当然最好的办法是同时综合使用上述3种方法,下面就DBCP和C3P0分别做一说明,假设wait_timeout为默认的8小时
1.DBCP增加以下配置信息:
//set to 'SELECT 1'
validationQuery = "SELECT 1"
//set to 'true'
testWhileIdle = "true"
//some positive integer
timeBetweenEvictionRunsMillis = 3600000
//set to something smaller than 'wait_timeout'
minEvictableIdleTimeMillis = 18000000
//if you don't mind a hit for every getConnection(), set to "true"
testOnBorrow = "true"
2.C3P0增加以下配置信息:
//获取connnection时测试是否有效
testConnectionOnCheckin = true
//自动测试的table名称
automaticTestTable=C3P0TestTable
//set to something much less than wait_timeout, prevents connections from going stale
idleConnectionTestPeriod = 18000
//set to something slightly less than wait_timeout, preventing 'stale' connections from being handed out
maxIdleTime = 25000
//if you can take the performance 'hit', set to "true"
testConnectionOnCheckout = true
还有另一个博主的解决方案:
(1)增加wait_timeout的时间。
(2)测试连接池中的connection的有效性。
可以使用hibernate等持久化管理框架,如使用配置:
<property name=”connection.autoReconnect”>true</property> <!–这个是最主要的–>
<property name=”connection.autoReconnectForPools”>true</property>
<property name=”connection.is-connection-validation-required”>true</property
也可以在Mysql的url中加入autoReconnect=true。
在data source 配置时加入下面三行也可以解决问题:
<property name=”connection.autoReconnect”>true</property> <!–这个是最主要的–>
<property name=”connection.autoReconnectForPools”>true</property>
<property name=”connection.is-connection-validation-required”>true</property
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after connection closed.
一直没办法解决,就到网上看了别人的博客,下面是转载的内容:
分析,出现这种异常的原因是:
Mysql服务器默认的“wait_timeout”是8小时,也就是说一个connection空间超过8个小时,Mysql将自动断开该connection,这就是问题所在,在连接池中的connection如果空闲超过8小时,mysql将其断开,连接池并不知道该connection已失效,如果这时有client请求connection,连接池将失效的connection提供给client,将会造成上面的异常。
解决的方法有3种:
增加wait_timeout的时间。
减少Connection pools中connection的lifetime。
测试Connection pools中connection的有效性。
当然最好的办法是同时综合使用上述3种方法,下面就DBCP和C3P0分别做一说明,假设wait_timeout为默认的8小时
1.DBCP增加以下配置信息:
//set to 'SELECT 1'
validationQuery = "SELECT 1"
//set to 'true'
testWhileIdle = "true"
//some positive integer
timeBetweenEvictionRunsMillis = 3600000
//set to something smaller than 'wait_timeout'
minEvictableIdleTimeMillis = 18000000
//if you don't mind a hit for every getConnection(), set to "true"
testOnBorrow = "true"
2.C3P0增加以下配置信息:
//获取connnection时测试是否有效
testConnectionOnCheckin = true
//自动测试的table名称
automaticTestTable=C3P0TestTable
//set to something much less than wait_timeout, prevents connections from going stale
idleConnectionTestPeriod = 18000
//set to something slightly less than wait_timeout, preventing 'stale' connections from being handed out
maxIdleTime = 25000
//if you can take the performance 'hit', set to "true"
testConnectionOnCheckout = true
还有另一个博主的解决方案:
(1)增加wait_timeout的时间。
(2)测试连接池中的connection的有效性。
可以使用hibernate等持久化管理框架,如使用配置:
<property name=”connection.autoReconnect”>true</property> <!–这个是最主要的–>
<property name=”connection.autoReconnectForPools”>true</property>
<property name=”connection.is-connection-validation-required”>true</property
也可以在Mysql的url中加入autoReconnect=true。
在data source 配置时加入下面三行也可以解决问题:
<property name=”connection.autoReconnect”>true</property> <!–这个是最主要的–>
<property name=”connection.autoReconnectForPools”>true</property>
<property name=”connection.is-connection-validation-required”>true</property
相关文章推荐
- MySQLNonTransientConnectionException: No operations allowed after statement closed
- nutz连接mysql异常处理:MySQLNonTransientConnectionException: No operations allowed after connection closed
- nutz连接mysql异常处理:MySQLNonTransientConnectionException: No operations allowed after connection closed
- Mysql异常:MySQLNonTransientConnectionException: No operations allowed after statement closed
- Mysql异常:MySQLNonTransientConnectionException: No operations allowed after statement closed
- Mysql异常:MySQLNonTransientConnectionException: No operations allowed after statement closed
- Mysql异常:MySQLNonTransientConnectionException: No operations allowed after statement closed
- Mysql异常:MySQLNonTransientConnectionException: No operations allowed after statement closed
- MySQLNonTransientConnectionException: No operations allowed after connection closed.
- 连接mysql异常处理:MySQLNonTransientConnectionException: No operations allowed after connection closed
- com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: No operations allowed after connec
- MySQLNonTransientConnectionException: No operations allowed after connection closed
- MySQL: No operations allowed after connection closed。解决办法
- MyBatis连接MySQL报异常:No operations allowed after connection closed.Connection was implicitly closed
- mysql No operations allowed after connection closed连接异常的解决
- MyBatis连接MySQL出错:No operations allowed after connection closed
- MySQL - No operations allowed after connection closed.;
- myBatis连接MySQL报异常:No operations allowed after connection closed.Connection was i
- myBatis连接MySQL报异常:No operations allowed after connection closed.Connection was implicitly closed
- myBatis连接MySQL报异常:No operations allowed after connection closed.Connection was implicitly closed