[DERBY-3596] Creation of logical connections from a pooled connection causes resource leak on the server

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.2.2.0, 10.3.2.1, 10.4.1.3, 10.5.1.1
• Fix Version/s: 10.4.2.0, 10.5.1.1
• Component/s: Network Client, Network Server
• Bug behavior facts: Performance
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 04/Apr/08 14:11
• Updated: 29/Jun/09 13:47
• Resolved: 30/Jun/08 07:42

Description

When using ClientConnectionPoolDataSource and connection pooling, a new connection / transaction is created for every new logical connection, and the resources are not freed / cleaned up in the server. They are not even cleaned up when the physical connection (ClientPooledConnection) is closed.
A logical connection is obtained by invoking ClientPooledConnection.getConnection().

I have observed that if you run the repro enough times against the same server, the number of transaction in the transaction table will be reduced now and then. I believe this is garbage collection, but I have not investigated the problem enough to tell for sure what's going on.

I have also seen some locks not being freed, causing timeouts in some applications. I don't have a repro for the lock problem at this time, but it is very likely related to this issue.

Note that XA connections are handled differently on the server, and do probably not have this problem.

Issue Links

• is related to: DERBY-3313 JDBC client driver statement cache