jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-1636) Make shutdown hooks in TransientFileFactory removable
Date Wed, 02 Jul 2008 23:36:45 GMT

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

Alexander Klimetschek closed JCR-1636.

    Resolution: Fixed

Once a patch is applied to svn and the bug is closed, it is better to create another issue
instead of re-opening. You can link to this bug with "relates to" to connect the dots. The
new JCR-1668 you created is a good fit - I created the link and close this bug, could you
upload your patch to the other issue and provide the comments (so they are coming directly
from you and not from me)?

> Make shutdown hooks in TransientFileFactory removable
> -----------------------------------------------------
>                 Key: JCR-1636
>                 URL: https://issues.apache.org/jira/browse/JCR-1636
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-commons
>    Affects Versions: 1.4, commons 1.4.2
>            Reporter: Roman Puchkovskiy
>             Fix For: 1.5
>         Attachments: JCR-1636-reaper-thread.patch, JCR-1636-workaround.patch
> TransientFileFactory class always registers shutdown hook. So, if jackrabbit classes
were loaded by web-app classloader, they will not be released when web-app is undeployed (if
jackrabbit-jcr-commons JAR is inside WAR). This causes classloader leak.
> It seems to be useful to have ability to cancel TransientFileFactory's shutdown hook
when application is going to be unloaded to avoid classloader leak.

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

View raw message