[
https://issues.apache.org/jira/browse/DERBY-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046878#comment-13046878
]
Dag H. Wanvik commented on DERBY-5108:
--------------------------------------
Re cleanUpOnError: I believe the Throwable can be an SQLException, but
essentially anything. The InterruptedExceptions
are handled, I think, before we get this far, although I think I saw a couple
of unhandled wait's the other day which is on my list of things to check.
But there could be other unhandled Exceptions and Errors as well, cf. the call
to DCI#cleanUpOnError from ContextManager#cleanupOnError.called from
TRI#handleException called from EmbedConnection#handleException which is called
from many API methods in catch-all (Throwable) constructs.
EmbedConnection#handleException is also called from
ConnectionChild#handleException which is used from ResultSet API methods etc...
Note the call to wrap "other" exceptions in the call TRI#warpInSQLException
towards the end of TRI#handleException.
> Intermittent failure in
> AutomaticIndexStatisticsTest.testShutdownWhileScanningThenDelete on Windows
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-5108
> URL: https://issues.apache.org/jira/browse/DERBY-5108
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.1.2
> Environment: Windows platforms.
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Blocker
> Fix For: 10.9.0.0
>
> Attachments: derby-5108-1a-early_istats_shutdown.diff,
> derby-5108-2.diff, derby-5108-2a-early_istats_shutdown_broad.diff,
> derby-5108-3a-istat_log_abort.diff, javacore.20110309.125807.4048.0001.txt,
> waitOnShutdown.diff
>
>
> The test AutomaticIndexStatisticsTest.testShutdownWhileScanningThenDelete
> fails intermittently on Windows platforms because the test is unable to
> delete a database directory.
> Even after several retries and sleeps (the formula should be (attempt -1) *
> 2000, resulting in a total sleep time of 12 seconds), the conglomerate
> system\singleUse\copyShutdown\seg0\c481.dat cannot be deleted.
> For instance from
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/w2003/1078855-suitesAll_diff.txt
> :
> (truncated paths)
> testShutdownWhileScanningThenDelete <assertDirectoryDeleted> attempt 1 left 3
> files/dirs behind: 0=system\singleUse\copyShutdown\seg0\c481.dat
> 1=system\singleUse\copyShutdown\seg0 2=system\singleUse\copyShutdown
> <assertDirectoryDeleted> attempt 2 left 3 files/dirs behind:
> 0=system\singleUse\copyShutdown\seg0\c481.dat
> 1=system\singleUse\copyShutdown\seg0 2=system\singleUse\copyShutdown
> <assertDirectoryDeleted> attempt 3 left 3 files/dirs behind:
> 0=system\singleUse\copyShutdown\seg0\c481.dat
> 1=system\singleUse\copyShutdown\seg0 2=system\singleUse\copyShutdown
> <assertDirectoryDeleted> attempt 4 left 3 files/dirs behind:
> 0=system\singleUse\copyShutdown\seg0\c481.dat
> 1=system\singleUse\copyShutdown\seg0 2=system\singleUse\copyShutdown
> used 205814 ms F.
> Maybe the database isn't shut down, or some specific timing of events causes
> a file to be reopened when it shouldn't have been (i.e. after the database
> shutdown has been initiated).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
