[ 
https://issues.apache.org/jira/browse/DERBY-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Waagan updated DERBY-3596:
-----------------------------------

    Attachment: ConnectionPoolingBug.java

Attached repro 'ConnectionPoolingBug.java'.
It runs a test sequence and prints the number of entries in the transaction 
table.
You must start a network server manually, and run the repro multiple times to 
see the GC happening on the server.

> Creation of logical connections from a pooled connection causes resource leak 
> on the server
> -------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3596
>                 URL: https://issues.apache.org/jira/browse/DERBY-3596
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client, Network Server, Performance
>    Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.2.1, 10.4.1.0, 10.5.0.0
>            Reporter: Kristian Waagan
>         Attachments: ConnectionPoolingBug.java
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to