commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Hohwiller (JIRA) <>
Subject [jira] Created: (DBCP-277) DBCP Locking Up
Date Tue, 02 Dec 2008 09:28:45 GMT
DBCP Locking Up

                 Key: DBCP-277
             Project: Commons Dbcp
          Issue Type: Bug
    Affects Versions: 1.2.2
            Reporter: Jörg Hohwiller

We had hanging threads that stalled in SocketInputStream.socketRead0 via Oracle-JDBC-Driver
in our tomcat. 
Because we found DBCP-28, we decided to update to version 1.2.2 of commons-dbcp.
Since that our Problems got worse because we experience some sort of deadlock in commons-dbcp.

Thread-Dumps after a nightly loadtest expose that threads got stuck in GenericObjectPool.returnObject,
while others wait in borrowObject. 
We stopped the load and waited for hours. The thread-dump still looks the same:

"TP-Processor1361" daemon prio=1 tid=0x67379fb8 nid=0x36e9 waiting for monitor entry [0x5f5cb000..0x5f5cc0c0]
	at org.apache.commons.pool.impl.GenericObjectPool.returnObject(
	- waiting to lock <0x716c4e50> (a org.apache.commons.pool.impl.GenericObjectPool)
	at org.apache.commons.dbcp.PoolableConnection.close(
	- locked <0x7a6d0408> (a org.apache.commons.dbcp.PoolableConnection)
	at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(
	at org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.closeConnection(
	at org.hibernate.jdbc.ConnectionManager.closeConnection(
	at org.hibernate.jdbc.ConnectionManager.cleanup(
	at org.hibernate.jdbc.ConnectionManager.close(
	at org.hibernate.impl.SessionImpl.close(
	at org.springframework.orm.hibernate3.SessionFactoryUtils.closeSession(
	at org.springframework.orm.hibernate3.SessionFactoryUtils.closeSessionOrRegisterDeferredClose(
	at org.springframework.orm.hibernate3.HibernateTransactionManager.doCleanupAfterCompletion(

The same issue was already discussed on the mailing-list so we are not the only ones with
this problem:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message