[DERBY-5495] Master issue to track fixes to sequence generators

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: SQL
• Labels: derby_backport_reject_10_8 derby_triage10_9
• Urgency: Blocker
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 07/Nov/11 14:30
• Updated: 14/Jun/13 17:18
• Resolved: 15/May/12 17:58

Description

This is a master issue to which we can link issues with sequence/identity generators.

Issue Links

• is related to: DERBY-5671 NsTest does not run on trunk do multiple issues stemming from concurrency improvements
• relates to: DERBY-5422 IndexOutOfBoundsException followed by NullPointerException in cleanup during system.nstest
• relates to: DERBY-5428 ns test error: ERROR 38000: The exception 'org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED Identity being changed on a live cacheable. Old uuidString = 846c00a0-0132-88d8-fec0-000000080920' was thrown while evaluating an expression
• relates to: DERBY-5430 Embedded nstest shows ERROR 40001: A lock could not be obtained due to a deadlock, in nstest
• relates to: DERBY-5493 Same value returned by successive calls to a sequence generator.
• relates to: DERBY-5494 Same value returned by successive calls to a sequence generator flanking an unorderly shutdown.
• relates to: DERBY-5486 Upgrade tests should verify that DERBY-4437 was backed out of 10.8.2.2
• relates to: DERBY-5443 reduce number of times sequence updater does it work on user thread rather than nested user thread.
• relates to: DERBY-5471 Stress test for identity columns and sequence seem to be taking longer on trunk compared to 10.8.2.2 RC3