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] Resolved: (DERBY-1439) Investigate removing the antiGC thread in embedded Derby
Date Tue, 26 Oct 2010 13:50:19 GMT

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

Knut Anders Hatlen resolved DERBY-1439.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.7.1.0
    Issue & fix info:   (was: [Patch Available])

I've committed the patch (revision 1027552) so that we get more testing of it before 10.7.
Hopefully, it doesn't cause any problems, but if it does, we can back it out from the 10.7
branch.

> Investigate removing the antiGC thread in embedded Derby
> --------------------------------------------------------
>
>                 Key: DERBY-1439
>                 URL: https://issues.apache.org/jira/browse/DERBY-1439
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>            Reporter: Daniel John Debrunner
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.7.1.0
>
>         Attachments: d1439.diff, patch1.diff
>
>
> The antiGC thread was originally created to avoid the DriverManager class being garbage
collected when no refrences existed to it and it had loaded the embedded JDBC driver (and
hence shutting down the engine). This was an issue with JDK 1.1. Since Derby does not support
jdk1.1 and garbage collection of classes is clearly defined, it is possible the thread serves
no useful purpose.

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


Mime
View raw message