Richard Mixon wrote:
Marc,
Thank you - We are using a recent version of the MySQL Connector/J (3.1.10),
but maybe that does not mean anything.
- Richard
Hmm thats not very recent. I know of 2 bugs since then that have bitten
me. 3.1.13 should be brewing and that would be the first
Can you change your code to something similar to below? I have seen issues
with certain implementations of database drivers in which the JDBC interfaces
are not being implemented/coded properly.
Just remember that the order you call your close statements does matter
(although yours looked
I'm still curious about the crazy logAbandoned messages - not sure how to
interpret or rely on them. I'll try a again with a briefer posting - maybe I
was too detailed in the original post.
We are getting strange (erroneous?) messages because of the logAbandoned
parameter:
1) The dates look
JDBC connection leak using removeAbandoned parm
Can you change your code to something similar to below? I have seen issues
with certain implementations of database drivers in which the JDBC
interfaces are not being implemented/coded properly.
Just remember that the order you call your close
version of the MySQL Connector/J (3.1.10),
but maybe that does not mean anything.
- Richard
-Original Message-
From: Farrow, Marc [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 4:44 AM
To: Tomcat Users List
Subject: RE: Diagnosing DBCP JDBC connection leak using
#1 Could be a logging bug. Notice how the day is always the same as the
minute.
On 4/5/06, Richard Mixon [EMAIL PROTECTED] wrote:
I'm still curious about the crazy logAbandoned messages - not sure how to
interpret or rely on them. I'll try a again with a briefer posting - maybe
I
was too
