db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3875) Derby cannot replace a database after encountering corruption
Date Wed, 08 Oct 2008 17:49:44 GMT

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

Myrna van Lunteren commented on DERBY-3875:

I think it's better to keep the assert and make the catch clause in RAFContainer.openContainer
I looked briefly at catching an Exception, but that gets to be quite a big change, requiring
adding throwing Exceptions in many places, and is that really necessary?
SanityManager.Asserts are RuntimeExceptions, and, very helpfully, you don't need to declare
So, all we need is to add a catch for RuntimeException:
        catch  (PrivilegedActionException pae) {
             throw (StandardException) pae.getException();
        catch (RuntimeException e) {
            throw e;

I think that will do...

> Derby cannot replace a database after encountering corruption
> -------------------------------------------------------------
>                 Key: DERBY-3875
>                 URL: https://issues.apache.org/jira/browse/DERBY-3875
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:
>         Environment: ------------------ Java Information ------------------
> Java Version:    1.6.0_06
> Java Vendor:     Sun Microsystems Inc.
> Java home:       C:\Program Files\Java\jre1.6.0_06
> Java classpath:  C:\Working\Derby-fileclose-fix\bin;C:\Working\Derby-fileclose-fix\lib\derby.jar
> OS name:         Windows XP
> OS architecture: x86
> OS version:      5.1
> Java user name:  Administrator
> Java user home:  C:\Documents and Settings\Administrator
> Java user dir:   C:\Working\Derby-fileclose-fix
> java.specification.name: Java Platform API Specification
> java.specification.version: 1.6
> --------- Derby Information --------
> JRE - JDBC: Java SE 6 - JDBC 4.0
> [C:\Working\Derby-fileclose-fix\lib\derby.jar] - (689064)
> ------------------------------------------------------
> ----------------- Locale Information -----------------
> ------------------------------------------------------
>            Reporter: Jason McLaurin
>         Attachments: derby-3875-BackupRestoreTest.diff, derby-3875-BackupRestoreTest.stat,
DERBY-3875_tst1.diff, FileCloseBugDemo.java, FileCloseBugDemo.java, RAFContainerPatch.txt
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> When Derby encounters a corrupt data file, it does not close the data file before throwing
an exception to the caller.  If the user tries to replace the database with a backup in response
to the corruption, Derby will first attempt to delete the contents of the corrupt database.
 But since the corrupt file was never closed, it cannot be deleted, and Derby fails to start.
> The attached java code should reproduce the problem, and the attached patch should fix

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

View raw message