db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5336) Repeated database creation causes OutOfMemoryError
Date Wed, 20 Jul 2011 12:43:58 GMT

     [ 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)
      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

> 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:
>         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


View raw message