db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3131) Background cleaner has no daemon service after database creation
Date Wed, 17 Oct 2007 11:16:50 GMT

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

Knut Anders Hatlen commented on DERBY-3131:

To reproduce put some println statements in Clock.useDaemonService() and try this in ij:

ij version 10.4
ij> connect 'jdbc:derby:mydb;create=true';  
ij> disconnect;
ij> connect 'jdbc:derby:mydb;shutdown=true';
ERROR 08006: Database 'mydb' shutdown.
ij> connect 'jdbc:derby:mydb';
name: ContainerCache
name: PageCache

useDaemonService() is not called on the first boot, but it is called on the second boot.

> 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:
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
> 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.

View raw message