db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6329) Recognize and log to derby.log when Derby is running in unsupported environments like write caching enabled.
Date Fri, 30 Aug 2013 17:03:52 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754903#comment-13754903
] 

Mike Matrigali commented on DERBY-6329:
---------------------------------------

not sure how to do this.  Maybe need to ask for new features in the JVM to tell us when
the JVM call to sync a file block is not supported.
                
> 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
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message