Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
10.8.2.2
-
None
Description
New errors were seen while running NsTest against the 10.8.2 release candidates. These errors are recorded as DERBY-5430 and DERBY-5422. The first error is a deadlock which occurs when inserting into the main table of the test. The second error is a problem clearing the identity cache. These errors have caused people to lose confidence in the concurrency improvements introduced by DERBY-4437. We should back the DERBY-4437 changes out of the 10.8 branch and use the trunk to continue debugging the problems disclosed by NsTest.
Attachments
Attachments
Issue Links
- relates to
-
DERBY-5422 IndexOutOfBoundsException followed by NullPointerException in cleanup during system.nstest
- Closed
-
DERBY-5671 NsTest does not run on trunk do multiple issues stemming from concurrency improvements
- Closed
-
DERBY-5430 Embedded nstest shows ERROR 40001: A lock could not be obtained due to a deadlock, in nstest
- Closed
-
DERBY-5454 ERROR 40001 deadlock in nstest on select max(serialkey)
- Closed
-
DERBY-4437 Concurrent inserts into table with identity column perform poorly
- Closed