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] Updated: (DERBY-4432) Memory leak when attempting to boot non-existing database with the in-memory back end
Date Thu, 12 Nov 2009 08:33:39 GMT

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

Kristian Waagan updated DERBY-4432:

    Attachment: releaseNote.html

Back-ported patch 1a to the 10.5 branch with revision 835290.
Attached first revision of a release note, as the change may break existing applications using
the in-memory back end. The incompatibility will normally not be triggered, which is why I
chose to back-port the fix.

> Memory leak when attempting to boot non-existing database with the in-memory back end
> -------------------------------------------------------------------------------------
>                 Key: DERBY-4432
>                 URL: https://issues.apache.org/jira/browse/DERBY-4432
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:,
>         Environment: In-memory back end and large amount of boot attempts of non-existing
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For:
>         Attachments: derby-4432-1a-mem_leak_fix.diff, derby-4432-1a-mem_leak_fix.stat,
> When attempting to boot a non-existing database with the in-memory back end, a DataStore
is created and referenced by a map. Since the database doesn't exist, Derby won't use the
DataStore again and it will hang around indefinitely in VFMemoryStorageFactory (or until the
same database is actually created, in which case the data store will be used).
> FYI, storage factory instances are instantiated liberally, including for the same service
(i.e. six instances of VFMemoryStorageFactory may be created to boot "jdbc:derby:memory:myDB").

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message