[jira] [Updated] (DERBY-5336) Repeated database creation causes OutOfMemoryError
[ https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-5336: --- Attachment: derby-5336-2a-regression_test.diff Thanks, Aja. Attaching patch 2a, where I copied Aja's repro and modified it to fit with the Derby test framework (JUnit based): - switched from DriverManager to DataSource - replaced commons io call to delete directory - added an extra sanity check - added test as testRepeatedDatabaseCreationWithAutoStats in memory.MemoryLeakFixesTest. Should be run with 'ant junit-lowmem' (after building Derby), which uses a 16 MB heap. The test failed when run without the fix, it succeeded with patch 1a applied. Patch ready for review. > Repeated database creation causes OutOfMemoryError > -- > > Key: DERBY-5336 > URL: https://issues.apache.org/jira/browse/DERBY-5336 > Project: Derby > Issue Type: Bug > Components: Services >Affects Versions: 10.8.1.2 > Environment: Windows 7 64-bit, jdk1.6.0_26 >Reporter: Aja Walker >Assignee: Kristian Waagan > Attachments: DerbyOutOfMemoryErrorRepro.java, LicensedRepro.java, > derby-5336-1a-remove_context_on_stop.diff, derby-5336-2a-regression_test.diff > > > Repeatedly creating, querying, updating, and shutting down a database or > databases eventually causes OutOfMemoryError. > Java source reproducing the problem is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5336) Repeated database creation causes OutOfMemoryError
[ https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aja Walker updated DERBY-5336: -- Attachment: LicensedRepro.java Attaching the repro source with the license box ticked this time. > Repeated database creation causes OutOfMemoryError > -- > > Key: DERBY-5336 > URL: https://issues.apache.org/jira/browse/DERBY-5336 > Project: Derby > Issue Type: Bug > Components: Services >Affects Versions: 10.8.1.2 > Environment: Windows 7 64-bit, jdk1.6.0_26 >Reporter: Aja Walker >Assignee: Kristian Waagan > Attachments: DerbyOutOfMemoryErrorRepro.java, LicensedRepro.java, > derby-5336-1a-remove_context_on_stop.diff > > > Repeatedly creating, querying, updating, and shutting down a database or > databases eventually causes OutOfMemoryError. > Java source reproducing the problem is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5336) Repeated database creation causes OutOfMemoryError
[ https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-5336: --- Attachment: derby-5336-1a-remove_context_on_stop.diff Attached patch 1a, which removes the istat daemon context by invoking the cleanup code in the system context. Tests passed on Linux and Solaris 11 using Java 6. Patch ready for review. > Repeated database creation causes OutOfMemoryError > -- > > Key: DERBY-5336 > URL: https://issues.apache.org/jira/browse/DERBY-5336 > Project: Derby > Issue Type: Bug > Components: Services >Affects Versions: 10.8.1.2 > Environment: Windows 7 64-bit, jdk1.6.0_26 >Reporter: Aja Walker >Assignee: Kristian Waagan > Attachments: DerbyOutOfMemoryErrorRepro.java, > derby-5336-1a-remove_context_on_stop.diff > > > Repeatedly creating, querying, updating, and shutting down a database or > databases eventually causes OutOfMemoryError. > Java source reproducing the problem is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5336) Repeated database creation causes OutOfMemoryError
[ https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-5336: --- Issue & fix info: [Patch Available, Repro attached, Workaround attached] (was: [Workaround attached, Repro attached]) > Repeated database creation causes OutOfMemoryError > -- > > Key: DERBY-5336 > URL: https://issues.apache.org/jira/browse/DERBY-5336 > Project: Derby > Issue Type: Bug > Components: Services >Affects Versions: 10.8.1.2 > Environment: Windows 7 64-bit, jdk1.6.0_26 >Reporter: Aja Walker >Assignee: Kristian Waagan > Attachments: DerbyOutOfMemoryErrorRepro.java, > derby-5336-1a-remove_context_on_stop.diff > > > Repeatedly creating, querying, updating, and shutting down a database or > databases eventually causes OutOfMemoryError. > Java source reproducing the problem is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5336) Repeated database creation causes OutOfMemoryError
[ https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-5336: -- Component/s: (was: Miscellaneous) Services Issue & fix info: [Repro attached, Workaround attached] (was: [Repro attached]) Bug behavior facts: [Crash, Regression] (was: [Crash]) I'm able to reproduce the OOME on trunk. It looks like the objects belonging to the stopped database instances are still referenced from the index statistics update daemon and cannot be freed. Disabling automatic update of index statistics seems to work around the problem. If I run the repro with -Dderby.storage.indexStats.auto=false, I don't see the OOME. I'm marking this bug as a regression, since the OOME is not seen with 10.7.1.1. > Repeated database creation causes OutOfMemoryError > -- > > Key: DERBY-5336 > URL: https://issues.apache.org/jira/browse/DERBY-5336 > Project: Derby > Issue Type: Bug > Components: Services >Affects Versions: 10.8.1.2 > Environment: Windows 7 64-bit, jdk1.6.0_26 >Reporter: Aja Walker > Attachments: DerbyOutOfMemoryErrorRepro.java > > > Repeatedly creating, querying, updating, and shutting down a database or > databases eventually causes OutOfMemoryError. > Java source reproducing the problem is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5336) Repeated database creation causes OutOfMemoryError
[ https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aja Walker updated DERBY-5336: -- Description: Repeatedly creating, querying, updating, and shutting down a database or databases eventually causes OutOfMemoryError. Java source reproducing the problem is attached. was: Creating, querying, updating, and shutting down multiple databases eventually causes OutOfMemoryError. Java source reproducing the problem is attached. Summary: Repeated database creation causes OutOfMemoryError (was: Creation of multiple databases causes OutOfMemoryError) > Repeated database creation causes OutOfMemoryError > -- > > Key: DERBY-5336 > URL: https://issues.apache.org/jira/browse/DERBY-5336 > Project: Derby > Issue Type: Bug > Components: Miscellaneous >Affects Versions: 10.8.1.2 > Environment: Windows 7 64-bit, jdk1.6.0_26 >Reporter: Aja Walker > Attachments: DerbyOutOfMemoryErrorRepro.java > > > Repeatedly creating, querying, updating, and shutting down a database or > databases eventually causes OutOfMemoryError. > Java source reproducing the problem is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
