We are using dbcp to configure db pooling.
I have many threads stuck like the one below. Any reason why this
would be . Seems like an odd place to be stuck. Does H2 limit the
number of connections or something?
"TP-Processor41" daemon prio=10 tid=0x00002aad4c60e000 nid=0x4e3f
waiting for monitor entry [0x0000000045c83000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.h2.command.Command.executeQuery(Command.java:130)
- waiting to lock <0x00002aaac118bd78> (a org.h2.engine.Database)
at
org.h2.jdbc.JdbcConnection.getInternalAutoCommit(JdbcConnection.java:
396)
at org.h2.jdbc.JdbcConnection.getAutoCommit(JdbcConnection.java:388)
- locked <0x00002aaac7530c48> (a org.h2.jdbc.JdbcConnection)
at
org.apache.commons.dbcp.DelegatingConnection.getAutoCommit(DelegatingConnection.java:
337)
at
org.apache.commons.dbcp.PoolableConnectionFactory.passivateObject(PoolableConnectionFactory.java:
684)
at
org.apache.commons.pool.impl.GenericObjectPool.addObjectToPool(GenericObjectPool.java:
1379)
at
org.apache.commons.pool.impl.GenericObjectPool.returnObject(GenericObjectPool.java:
1342)
at
org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:
90)
- locked <0x00002aaac7530b70> (a
org.apache.commons.dbcp.PoolableConnection)
at org.apache.commons.dbcp.PoolingDriver
$PoolGuardConnectionWrapper.close(PoolingDriver.java:273)
at
com.dotmarketing.cache.H2CacheLoader.closeConnection(H2CacheLoader.java:
452)
at
com.dotmarketing.cache.H2CacheLoader.doUnmarshall(H2CacheLoader.java:
401)
at
com.dotmarketing.cache.H2CacheLoader.loadAttributes(H2CacheLoader.java:
466)
at com.dotmarketing.cache.H2CacheLoader.get(H2CacheLoader.java:67)
......
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
