On 14/06/2010 09:07, elankumaran wrote:
Hi Filip Hanik,
We are using the dbcp 1.2.2 with Tomcat 5& 6 version. We are experiencing
the dead lock issue in the getNumIdle() method of GenericObjectPool class.
Can i update to dpcp 1.4 version in order to fix the issue?
That would be a question fo
dbcp.pool.impl.GenericObjectPool.returnObject(GenericObjectPool.java:1076)
>> at
>> org.apache.tomcat.dbcp.dbcp.PoolableConnection.close(PoolableConnection.java:87)
>> - locked <0x2aaabf3210f0> (a
>> org.apache.tomcat.dbcp.dbcp.PoolableConnection)
l.GenericObjectPool.returnObject(GenericObjectPool.java:1076)
>> at
>> org.apache.tomcat.dbcp.dbcp.PoolableConnection.close(PoolableConnection.java:87)
>> - locked <0x2aaabf3210f0> (a
>> org.apache.tomcat.dbcp.dbcp.PoolableConnection)
>>
I have submitted a patch for this to commons
https://issues.apache.org/jira/browse/DBCP-270
Filip
Metta wrote:
I'm running TC 6.0.16 on 64Bit RH Linux 5.1
We're seeing a deadlock in the tomcat-dbcp - looks like it's to do with the
abandoned connection checking. I thought 6.0.16 used the commo
Tomcat uses 1.2.2 in that version, so I would suggest not using the
background validation at this point
Filip
Metta wrote:
I'm running TC 6.0.16 on 64Bit RH Linux 5.1
We're seeing a deadlock in the tomcat-dbcp - looks like it's to do with the
abandoned connection checking. I thought 6.0.16 us
PoolableConnection.close(PoolableConnection.java:87)
- locked <0x2aaabf3210f0> (a
org.apache.tomcat.dbcp.dbcp.PoolableConnection)
--
View this message in context:
http://www.nabble.com/DBCP-Deadlock-tp17999703p17999703.html
Sent from the Tomcat - Dev mailing list archive at Nabble.