[
https://issues.apache.org/jira/browse/DERBY-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-5406:
----------------------------------
Fix Version/s: 10.8.2.3
Assignee: Knut Anders Hatlen (was: Mike Matrigali)
backported change from trunk to 10.8. resetting original owner.
To backport farther back, this change may depend on other changes, as is
discussed in previous comments of this issue.
Hope is that this backport will elinate current intermittent failures in the
nightly tests against 10.8 as they did for trunk. At this point since this
issue is closed any new failures seen in these 2 tests in versions that have
the fix should be logged in a new issue and can
be linked back to this one
> Intermittent failures in CompressTableTest and TruncateTableTest
> ----------------------------------------------------------------
>
> Key: DERBY-5406
> URL: https://issues.apache.org/jira/browse/DERBY-5406
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.2.2, 10.9.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.8.2.3, 10.9.0.0
>
> Attachments: CompressAndPrepare.java,
> d5406-1a-detect-invalidation-during-compilation.diff, d5406-1b.diff,
> d5406-2a-invalidate-self.diff, d5406-3a.diff, d5406-4a-push-retry-logic.diff,
> d5406-4a-retry-on-conglomerate-error.diff
>
>
> The test cases CompressTableTest.testConcurrentInvalidation() and
> TruncateTableTest.testConcurrentInvalidation() fail intermittently with
> errors such as:
> ERROR XSAI2: The conglomerate (2,720) requested does not exist.
> The problem has been analyzed in the comments on DERBY-4275, and a patch
> attached to that issue (invalidation-during-compilation.diff) fixes the
> underlying race condition. However, that patch only works correctly together
> with the fix for DERBY-5161, which was backed out because it caused the
> regression DERBY-5280.
> We will therefore need to find a way to fix DERBY-5161 without reintroducing
> DERBY-5280 in order to resolve this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
