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
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?
Thread dump:
"http-8080-Processor17" daemon prio=10 tid=0x2aabdc01
Hi,
I'm running Tomcat 6.0.18 and still see this issue. Can you provide more
information about how one might disable background validation, or when a
version of Tomcat might be released does not contain this issue [1]? My
resource is currently defined like this:
I think that disabling backgrou
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
