[jira] Updated: (DBCP-352) Repeated calls to getMetadata in a transaction leads to performance degredation

[ https://issues.apache.org/jira/browse/DBCP-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Hulley updated DBCP-352: -- Attachment: commons-dbcp-1.4-patched.diff Patch diff Repeated calls to getMetadata in a transaction

[jira] Commented: (DBCP-352) Repeated calls to getMetadata in a transaction leads to performance degredation

[ https://issues.apache.org/jira/browse/DBCP-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993013#comment-12993013 ] Derek Hulley commented on DBCP-352: --- Results of running DBCPMetadataTest before and after

[jira] Commented: (DBCP-330) Calling getMetaData() without closing the connection lead to a memory leak

[ https://issues.apache.org/jira/browse/DBCP-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993015#comment-12993015 ] Derek Hulley commented on DBCP-330: --- See DBCP-352 patch and test results. Calling

[jira] Updated: (NET-258) Implement A Keepalive Mechanism

[ https://issues.apache.org/jira/browse/NET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Drozdowski updated NET-258: -- Attachment: ftp-keepalive.diff My ftp-keepalive patch provides this capability. Use

[jira] Commented: (DBCP-353) When DB Restarts(Bounce) the number ESTABLISHED DB connections exceeds its maximum configured limit.

[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993086#comment-12993086 ] Phil Steitz commented on DBCP-353: -- What versions of Commons DBCP and Pool are you using

[jira] Commented: (NET-258) Implement A Keepalive Mechanism

[ https://issues.apache.org/jira/browse/NET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993092#comment-12993092 ] Sebb commented on NET-258: -- Thanks for the patch. However, as it stands, it's not guaranteed to

[jira] Commented: (DBCP-353) When DB Restarts(Bounce) the number ESTABLISHED DB connections exceeds its maximum configured limit.

[ https://issues.apache.org/jira/browse/DBCP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993361#comment-12993361 ] Radhika Zawar commented on DBCP-353: dbcp version - commons-dbcp-1.2.2 pool version -