INFO - Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@309db823 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@234142af [ acquireIncrement -> 1, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 234142af, idleConnectionTestPeriod -> 0, initialPoolSize -> 1, maxIdleTime -> 120, maxPoolSize -> 100, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 1, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@7a8d0ae3 [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 7a8d0ae3, jdbcUrl -> jdbc:sqlserver://172.168.102.56:1432;databaseName=RTGSLiquidity, properties -> {useUnicode=true, user=******, password=******, characterEncoding=UTF-8} ], preferredTestQuery -> null, propertyCycle -> 300, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, usesTraditionalReflectiveProxies -> false ], factoryClassLocation -> null, identityToken -> 309db823, numHelperThreads -> 3 ]
WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5f9e08c9 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1a9c9d5e (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7c815e1f (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1); pendingTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@2b4ce455]
WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@171e8162 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3e0ce8dc (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1332b0f9 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1); pendingTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1f308679]
WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1a9c9d5e (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().
WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5f9e08c9 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().
WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7c815e1f (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt()
这是一段新日志，继续帮我分析
最新发布
本文介绍了一种在使用Hibernate框架时遇到的数据库连接死锁问题，并通过调整hibernate.c3p0.timeout参数来获取更多错误日志以帮助分析死锁原因。
扫一扫
3984
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
