You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Cédric Damioli (JIRA)" <ji...@apache.org> on 2013/01/17 14:12:23 UTC

[jira] [Updated] (JCR-3485) The Datastore garbage collector does not work with a Derby-based DbDataStore

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

Cédric Damioli updated JCR-3485:
--------------------------------

    Fix Version/s: 2.6

It is true that unit tests still don't pass with a DerbyDataStore, but this is another issue, I think.

I set this bug as targeted for 2.6, as it resolves the lock issues with Derby, and in my production scenario, allow garbage collector to run very well.
                
> The Datastore garbage collector does not work with a Derby-based DbDataStore
> ----------------------------------------------------------------------------
>
>                 Key: JCR-3485
>                 URL: https://issues.apache.org/jira/browse/JCR-3485
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.4.3
>            Reporter: Cédric Damioli
>             Fix For: 2.6
>
>         Attachments: DbDataStore.patch
>
>
> We obtain a lot of Derby lock timeouts
> Looking at the code, it seems that a few ResultSets are not actually closed, leading to Derby keeping some locks 

--
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