db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Sereda (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5963) Memory leak when shutting down Derby system
Date Sat, 27 Oct 2012 15:39:12 GMT

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

Igor Sereda updated DERBY-5963:

    Attachment: yourkit.png
> Memory leak when shutting down Derby system
> -------------------------------------------
>                 Key: DERBY-5963
>                 URL: https://issues.apache.org/jira/browse/DERBY-5963
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:,
>         Environment: Embedded Derby
> Windows 7
> java version "1.6.0_31"
> Java(TM) SE Runtime Environment (build 1.6.0_31-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
>            Reporter: Igor Sereda
>         Attachments: yourkit.png
> I am using an embedded Derby on a server within OSGi environment, as a private library
in my bundle. When the bundle is deactivated, I stop Derby database (with jdbc:derby:;shutdown=true;deregister=true
> But although otherwise the database is released, an instance of ContextManager stays
in memory due to a leaked reference in a ThreadLocal variable (from ContextService, I presume).
The instance of ContextManager is a big deal, because it also holds the whole page cache in
memory (40MB), and also, via class loader, holds whole my OSGi bundle too.
> Please let me know if you need any information on reproducing this problem.
> Thanks!
> Igor

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message