[jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-26 Thread Jeff Clary (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Clary updated DERBY-2480: -- Derby Info: [Patch Available] > DriverManager.getConnection leaks memory using EmbeddedDriver on non-ex

[jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-26 Thread Jeff Clary (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Clary updated DERBY-2480: -- Attachment: DERBY-2480-1.diff At Dag's suggestion I have attached a patch that addresses only DERBY-248

Re: [jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-23 Thread Dag H. Wanvik
"Jeff Clary (JIRA)" <[EMAIL PROTECTED]> writes: > This might be a bit premature, but I am attaching a patch we are > trying locally to fix this problem and DERBY-1947. From our > analysis, it looks like we are missing some calls to > TransactionResourceImpl.cleanupOnError(). This is what I found

[jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-23 Thread Jeff Clary (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Clary updated DERBY-2480: -- Attachment: Patch_DERBY-1947_and_DERBY-2480.diff This might be a bit premature, but I am attaching a pa

[jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-23 Thread John H. Embretsen (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John H. Embretsen updated DERBY-2480: - Derby Info: (was: [Regression]) Affects Version/s: 10.0.2.0

[jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-23 Thread John H. Embretsen (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John H. Embretsen updated DERBY-2480: - Attachment: heap-server-Xmx32m.png I downloaded and modified the repro java file so that

[jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-22 Thread Kristian Waagan (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2480: --- Priority: Minor (was: Major) Derby Info: [Regression] Environme

[jira] Updated: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

2007-03-22 Thread Jeff Clary (JIRA)
[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Clary updated DERBY-2480: -- Attachment: testOpenOfMissingDatabase.java Small test program demonstrating bug. > DriverManager.getCo