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-4813) TriggerTests failed to apply log record to store
Date Thu, 23 Sep 2010 12:59:34 GMT

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

Knut Anders Hatlen commented on DERBY-4813:

I see that derby.log contains many occurrences of this message before the test fails:

------------  BEGIN ERROR MESSAGE -------------

new log file exist and cannot be deleted C:\cludev\jagtmp\autoderbyN_derbyall\suitesAll_1\log\system\wombat\log\log454.dat
------------  END ERROR MESSAGE -------------

The test run had a failure in StreamingColumnTest (an intermittent failure fixed in DERBY-4531
but not backported) before the problems in TriggersTest, so perhaps a file handle was left
open and caused problems when later trying to write to that file? It's a bit strange, though,
that so many other tests ran in between without any issues, but it may of course be that none
of those tests produced enough log files to hit that file.

Hmmm... So it seems this log454.dat file that we cannot delete, prevents us from switching
from log453.dat, and we just continue appending log records to file 453 until it exceeds the
maximum size. Would it be a more appropriate response to fail immediately in the case where
we cannot switch log files, and tell the user to force the removal of the file that's blocking

> TriggerTests failed to apply log record to store
> ------------------------------------------------
>                 Key: DERBY-4813
>                 URL: https://issues.apache.org/jira/browse/DERBY-4813
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:
>         Environment: Microsoft© Windows Server© 2008 - 6.0.6002 Service Pack 2
> Sun Microsystems Inc. java version 1.4.2_16
>            Reporter: Knut Anders Hatlen
>         Attachments: failure.zip
> This failure was seen when testing the Derby release candidate:
> 1) test5InsertAfterTriggerNoReferencingClause(org.apache.derbyTesting.functionTests.tests.memory.TriggerTests)java.sql.SQLException:
Log Record has been sent to the stream, but it cannot be applied to the store (Object null).
 This may cause recovery problems also.
> http://dbtg.foundry.sun.com/derby/test/
> Will attach logs and the database to the bug report.

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

View raw message