美文网首页
c3p0连接池超出maxPoolSize

c3p0连接池超出maxPoolSize

作者: zlmind | 来源:发表于2018-05-10 10:19 被阅读515次

c3p0连接池超出maxPoolSize回报以下错误:

Caused by: org.apache.ibatis.exceptions.PersistenceException:

### Error querying database.  Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: An attempt by a client to checkout a Connection has timed out.

### The error may exist in INF/classes/config/mybatis/phoneMapper.xml]

### The error may involve com.tuniu.finance.xff.auth.dao.AuthPhoneMapper.selectByMemberId

### The error occurred while executing a query

### Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: An attempt by a client to checkout a Connection has timed out.

at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30) ~[mybatis-3.3.1.jar:3.3.1]

at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:122) ~[mybatis-3.3.1.jar:3.3.1]

at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source) ~[na:na]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_91]

at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91]

at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:358) ~[mybatis-spring-1.2.1.jar:1.2.1]

... 66 common frames omitted

Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: An attempt by a client to checkout a Connection has timed out.

at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80) ~[spring-jdbc-4.3.8.RELEASE.jar:4.3.8.RELEASE]

at org.mybatis.spring.transaction.SpringManagedTransaction.openConnection(SpringManagedTransaction.java:83) ~[mybatis-spring-1.2.1.jar:1.2.1]

at org.mybatis.spring.transaction.SpringManagedTransaction.getConnection(SpringManagedTransaction.java:69) ~[mybatis-spring-1.2.1.jar:1.2.1]

at org.apache.ibatis.executor.BaseExecutor.getConnection(BaseExecutor.java:315) ~[mybatis-3.3.1.jar:3.3.1]

at org.apache.ibatis.executor.SimpleExecutor.prepareStatement(SimpleExecutor.java:75) ~[mybatis-3.3.1.jar:3.3.1]

at org.apache.ibatis.executor.SimpleExecutor.doQuery(SimpleExecutor.java:61) ~[mybatis-3.3.1.jar:3.3.1]

at org.apache.ibatis.executor.BaseExecutor.queryFromDatabase(BaseExecutor.java:303) ~[mybatis-3.3.1.jar:3.3.1]

at org.apache.ibatis.executor.BaseExecutor.query(BaseExecutor.java:154) ~[mybatis-3.3.1.jar:3.3.1]

at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:102) ~[mybatis-3.3.1.jar:3.3.1]

at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:82) ~[mybatis-3.3.1.jar:3.3.1]

at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source) ~[na:na]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_91]

at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91]

at org.apache.ibatis.plugin.Invocation.proceed(Invocation.java:49) ~[mybatis-3.3.1.jar:3.3.1]

at com.tuniu.finance.xff.auth.security.SecurityPlugin.interceptQuery(SecurityPlugin.java:53) ~[auth-intf-2.0.0.jar:na]

at com.tuniu.finance.xff.auth.security.SecurityPlugin.intercept(SecurityPlugin.java:76) ~[auth-intf-2.0.0.jar:na]

at org.apache.ibatis.plugin.Plugin.invoke(Plugin.java:61) ~[mybatis-3.3.1.jar:3.3.1]

at com.sun.proxy.$Proxy103.query(Unknown Source) ~[na:na]

at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:120) ~[mybatis-3.3.1.jar:3.3.1]

... 70 common frames omitted

Caused by: java.sql.SQLException: An attempt by a client to checkout a Connection has timed out.

at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118) ~[mchange-commons-java-0.2.11.jar:0.2.11]

at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:77) ~[mchange-commons-java-0.2.11.jar:0.2.11]

at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:690) ~[c3p0-0.9.5.2.jar:0.9.5.2]

at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:140) ~[c3p0-0.9.5.2.jar:0.9.5.2]

at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source) ~[na:na]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_91]

at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91]

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.8.RELEASE.jar:4.3.8.RELEASE]

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) ~[spring-aop-4.3.8.RELEASE.jar:4.3.8.RELEASE]

at com.sun.proxy.$Proxy45.getConnection(Unknown Source) ~[na:na]

at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111) ~[spring-jdbc-4.3.8.RELEASE.jar:4.3.8.RELEASE]

at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77) ~[spring-jdbc-4.3.8.RELEASE.jar:4.3.8.RELEASE]

... 88 common frames omitted

Caused by: com.mchange.v2.resourcepool.TimeoutException: A client timed out while waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePool@5fb57348 -- timeout at awaitAvailable()

at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1467) ~[c3p0-0.9.5.2.jar:0.9.5.2]

at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:644) ~[c3p0-0.9.5.2.jar:0.9.5.2]

at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:554) ~[c3p0-0.9.5.2.jar:0.9.5.2]

at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConnectionInUse(C3P0PooledConnectionPool.java:758) ~[c3p0-0.9.5.2.jar:0.9.5.2]

at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:685) ~[c3p0-0.9.5.2.jar:0.9.5.2]

... 97 common frames omitted

报错处的c3p0源码

/*

    * by the semantics of wait(), a timeout of zero means forever.

    */

    private void awaitAvailable(long timeout) throws InterruptedException, TimeoutException, ResourcePoolException

    {

        assert Thread.holdsLock( this );

        if (force_kill_acquires)

            throw new ResourcePoolException("A ResourcePool cannot acquire a new resource -- the factory or source appears to be down.");

        Thread t = Thread.currentThread();

        try

        {

            acquireWaiters.add( t );

            int avail;

            long start = ( timeout > 0 ? System.currentTimeMillis() : -1);

            if (Debug.DEBUG && Debug.TRACE == Debug.TRACE_MAX)

            {

                if ( logger.isLoggable( MLevel.FINE ) )

                    logger.fine("awaitAvailable(): " +

                                    (exampleResource != null ?

                                                    exampleResource :

                                    "[unknown]") );

                trace();

            }

            while ((avail = unused.size()) == 0)

            {

                // the if case below can only occur when 1) a user attempts a

                // checkout which would provoke an acquire; 2) this

                // increments the pending acquires, so we go to the

                // wait below without provoking postAcquireMore(); 3)

                // the resources are acquired; 4) external management

                // of the pool (via for instance unpoolResource()

                // depletes the newly acquired resources before we

                // regain this' monitor; 5) we fall into wait() with

                // no acquires being scheduled, and perhaps a managed.size()

                // of zero, leading to deadlock. This could only occur in

                // fairly pathological situations where the pool is being

                // externally forced to a very low (even zero) size, but

                // since I've seen it, I've fixed it.

                if (pending_acquires == 0 && managed.size() < max)

                    _recheckResizePool();

                this.wait(timeout);

                if (timeout > 0 && System.currentTimeMillis() - start > timeout)

                    throw new TimeoutException("A client timed out while waiting to acquire a resource from " + this + " -- timeout at awaitAvailable()");

                if (force_kill_acquires)

                    throw new CannotAcquireResourceException("A ResourcePool could not acquire a resource from its primary factory or source.");

                ensureNotBroken();

            }

        }

        finally

        {

            acquireWaiters.remove( t );

            if (acquireWaiters.size() == 0)

                this.notifyAll();

        }

    }

解决方案:

1.增加maxPoolSize大小

2.排查系统,减少db使用次数,优化代码

c3p0连接池使用情况查看

要开启jmx

相关文章

网友评论

      本文标题:c3p0连接池超出maxPoolSize

      本文链接:https://www.haomeiwen.com/subject/qifzrftx.html