Excellent information! I will try those immediately.
mitch
Christopher Schultz wrote:
> Mitch,
>
> On 12/10/2009 7:43 PM, Mitch Claborn wrote:
> > poolPreparedStatements="true"
> > driverClassName="com.mysql.jdbc.Driver"
> > validationQuery="select * fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mitch,
On 12/10/2009 7:43 PM, Mitch Claborn wrote:
> poolPreparedStatements="true"
> driverClassName="com.mysql.jdbc.Driver"
> validationQuery="select * from operator limit 1"
FWIW, this is a non-ideal valida
> From: Mitch Claborn [mailto:mi...@claborn.net]
> Subject: Re: deadlock in database connection pooling?
>
> Can I simply delete the tomcat version of dbcp (jar file) and drop in
> the 1.3 version from commons?
No, Tomcat renames the classes in the jar to avoid collisions with any
laborn [mailto:mi...@claborn.net]
>> Subject: deadlock in database connection pooling?
>>
>> I'm seeing several occurrences of deadlocks in Tomcat like the
>> following. Any clues? Definition of the Resource is below.
>>
>
> Want to give us a hint about
> From: Mitch Claborn [mailto:mi...@claborn.net]
> Subject: deadlock in database connection pooling?
>
> I'm seeing several occurrences of deadlocks in Tomcat like the
> following. Any clues? Definition of the Resource is below.
Want to give us a hint about what Tomcat
I'm seeing several occurrences of deadlocks in Tomcat like the
following. Any clues? Definition of the Resource is below.
Found one Java-level deadlock:
=
"http-8081-56":
waiting to lock monitor 0x08f50bd0 (object 0x560511f8, a
org.apache.tomcat.dbcp.pool.impl.Gene
