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 "Mike Matrigali (JIRA)" <ji...@apache.org> on 2014/01/08 23:32:50 UTC

[jira] [Updated] (DERBY-6329) Recognize and log to derby.log when Derby is running in unsupported environments like write caching enabled.

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

Mike Matrigali updated DERBY-6329:
----------------------------------

    Component/s: Store

> Recognize and log to derby.log when Derby is running in unsupported environments like write caching enabled.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6329
>                 URL: https://issues.apache.org/jira/browse/DERBY-6329
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>            Reporter: Mike Matrigali
>
> It would be good if we could somehow recognize when Derby is being run in an unsupported 
> environment, like write cache enabled and log a warning on Boot to derby.log informing that
> database recovery will not work.
> This could be similar to what the system does when the database is booted with
> derby.system.durability=test



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)