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

Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2007/12/03 10:29:43 UTC

[jira] Resolved: (DERBY-3131) Background cleaner has no daemon service after database creation

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

Knut Anders Hatlen resolved DERBY-3131.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0
       Derby Info:   (was: [Patch Available])

Committed revision 600457.

> Background cleaner has no daemon service after database creation
> ----------------------------------------------------------------
>
>                 Key: DERBY-3131
>                 URL: https://issues.apache.org/jira/browse/DERBY-3131
>             Project: Derby
>          Issue Type: Bug
>          Components: Services, Store
>    Affects Versions: 10.4.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: d3131.diff, d3131.stat
>
>
> When a database is booted, the page cache and the container cache are given a daemon service to perform operations in the background. This happens in BaseDataFileFactory.postRecovery(). When a new database is created this code is not executed (presumably because we don't perform recovery), so its background cleaner remains inactive until the database is rebooted. The background cleaner should be active after the first boot.

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