[jira] Closed: (SLING-826) derby.antiGC thread not stopped when Jackrabbit Server bundle is stopped

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger closed SLING-826.
-----------------------------------

    Resolution: Fixed

Added shutdownOnClose setting for Derby PM workspaces in the repository.xml file of the jcr/jackrabbit-server module in Rev. 734085. 

> derby.antiGC thread not stopped when Jackrabbit Server bundle is stopped
> ------------------------------------------------------------------------
>
>                 Key: SLING-826
>                 URL: https://issues.apache.org/jira/browse/SLING-826
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Jackrabbit Server 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JCR Jackrabbit Server 2.0.4
>
>
> When the Jackrabbit Server bundle is stopped, the derby.antiGC thread reamins active thus preventing the bundle class loader to be garbage collected. The Derby Persistence Manager can be configured such, that the database is shut down, when the repository is shut down. This should be done in our default configuration too.

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