aspose file tools*
The moose likes JDBC and the fly likes com.mysql.jdbc.Connection openConnections memory leak Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "com.mysql.jdbc.Connection openConnections memory leak" Watch "com.mysql.jdbc.Connection openConnections memory leak" New topic
Author

com.mysql.jdbc.Connection openConnections memory leak

John Farrel
Ranch Hand

Joined: May 24, 2010
Posts: 84

I am working on a system that pools JDBC MySQL connections.

It fell over the other day with an out of memory error.

Looking at the .hprof, it says that one MySQL JDBC connection has a retained size of 27Mb. According to the hprof that was all in the com.mysql.jdbc.Connection.openConnections field.
Why would this field be accumulating values, and is there any way to clear it?

John
Maneesh Godbole
Saloon Keeper

Joined: Jul 26, 2007
Posts: 10451
    
    8

Are you closing your connections when done?


[How to ask questions] [Donate a pint, save a life!] [Onff-turn it on!]
John Farrel
Ranch Hand

Joined: May 24, 2010
Posts: 84
Maneesh Godbole wrote:Are you closing your connections when done?


The pool is keeping connections alive for re-use as it should.

I've found the issue... the ResultSest and Statements using the connection aren't being closed, and a MySQL JDBC Connection keeps some sort of log of the those until the connection itself is closed.

However, it's possible to turn this functionality off by adding dontTrackOpenResources=true to the MySQL JDBC URL.

Martin Vajsar
Sheriff

Joined: Aug 22, 2010
Posts: 3610
    
  60

John Farrel wrote:However, it's possible to turn this functionality off by adding dontTrackOpenResources=true to the MySQL JDBC URL.

Instead of such hacks, I'd suggest to stick to best practices and explicitly close the Statements and ResultSets after use. Every (reasonable) JDBC tutorial says so.

You should call close() on connections obtained from connection pool too, of course. This is the correct way to return the connection to the pool (mentioning it because it isn't entirely clear from your post whether you're doing so). Some connection pools might ensure that resources created on that connection which weren't properly closed are freed, but this depends on the particular connection pool you're using.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: com.mysql.jdbc.Connection openConnections memory leak