jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3341) GarbageCollector should fail fast if there is a problem
Date Thu, 14 Jun 2012 12:09:42 GMT

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

Thomas Mueller updated JCR-3341:

    Assignee: Thomas Mueller
      Status: Patch Available  (was: Open)

A patch for the 2.2 branch is attached.
> GarbageCollector should fail fast if there is a problem
> -------------------------------------------------------
>                 Key: JCR-3341
>                 URL: https://issues.apache.org/jira/browse/JCR-3341
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.5
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>         Attachments: JCR-3341.patch
> The GarbageCollector installs an ObservationListener to ensure moved nodes are scanned
as well.
> If there is an exception in the ObservationListener, this exception is captured (lastException),
but only evaluated at the very end of the GC cycle, in Listener.stop() / GarbageCollector.stopScan()
which is called as part of sweep(), before deleting unused items.
> This is quite late. For a large repository, scanning might take a few hours.
> If such an exception occurs, scanning should stop within a reasonable time (fail fast),
and the exception should be thrown there.
> This is related to JCR-3340

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message