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

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen updated DERBY-3131:
--------------------------------------

    Attachment: d3131.stat
                d3131.diff

With the attached patch, the background cleaner is also started the first time a database is booted (verified with the repro posted above). I moved the starting of the background cleaner out of BaseDataFileFactory.postRecovery() to a separate method called setupCacheCleaner(). This method is now invoked at the end of LogToFile.recover() regardless of whether or not recovery actually has been performed.

I have started suites.All and derbyall.

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