Options

C3P0PooledConnectionPoolManager - deadlock

We are getting a weird issue since we have migrated some clients into vertica

 

Looks like there is an issue with the jdbc driver not closing the connection corretly.

 

Any idea what could have been causing this? is this a known issue in the 7.1 jdbc?

 

 

 

Name: C3P0PooledConnectionPoolManager[identityToken->2tigb8991wajq981fqksme|1721d4a9, dataSourceName->dw-3]-HelperThread-#2
State: BLOCKED on com.vertica.jdbc.jdbc4.S4DatabaseMetaData@5fc6b839 owned by: C3P0PooledConnectionPoolManager[identityToken->2tigb8991wajq981fqksme|1721d4a9, dataSourceName->dw-3]-HelperThread-#0
Total blocked: 316 Total waited: 1,607

Stack trace:
com.vertica.jdbc.common.SDatabaseMetaData.closeMetaData(Unknown Source)
com.vertica.jdbc.common.SConnection.closeChildObjects(Unknown Source)
- locked java.lang.Object@6046e605
com.vertica.jdbc.common.SConnection.close(Unknown Source)
- locked com.vertica.jdbc.VerticaJdbc4ConnectionImpl@7c8c6cbd
com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:629)
com.mchange.v2.c3p0.impl.NewPooledConnection.closeMaybeCheckedOut(NewPooledConnection.java:259)
- locked com.mchange.v2.c3p0.impl.NewPooledConnection@b544679
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:619)
com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:1024)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:648)

 

 

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file