db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (DERBY-5336) Repeated database creation causes OutOfMemoryError
Date Tue, 09 Aug 2011 11:15:27 GMT

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

Kristian Waagan reassigned DERBY-5336:
--------------------------------------

    Assignee: Kristian Waagan

Seems the context used by the istat deamon isn't removed when the database is shut down.
I'm running regression tests on a possible fix.

On a related note, I'm wondering if the context class loader should be set to null for the
istat daemon thread?

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

        

Mime
View raw message