Noel J. Bergman wrote:
Stefano Bagnara wrote:
Where did you read that mysql recommend to downgrade to 2.0.14
as a workaround for memory leaks?
See http://bugs.mysql.com/bug.php?id=20003, particularly the second
paragraph of the author's response.
Ok, I see, but this is not mysql AB recommending to downgrade, but the
user reporting this issue that say that *his* issue does not appear with
mm-mysql.
Of course I cannot be sure that the problem is in mm-mysql, but at least
the new connectors have an option (dontTrackOpenResources=true/false)
that helps to find out if the problem is in missing
statement/conn/resultset close calls.
The tracking of openresources has been introduced with connector/j 3+
and when using dontTrackOpenResources=true it should work like the old
mm-mysql. connector/j by default is much more likely to leak memory
because of application problems because if you don't manually handle
correctly the closing of objects generated he does not free them. The
old mm-mysql kept no references to this objects but was not JDBC compliant.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
