[DERBY-5137] Enable or remove Derby3980DeadlockTest

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.8.1.2
• Component/s: Test
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 15/Mar/11 22:25
• Updated: 16/Feb/12 00:33

Description

As part of early work on DERBY-3980, I checked in an unrun test for this issue when I was working on it a long time ago, Derby3980DeadlockTest.

I verified it does pass now but maybe the new DeadLockDetectionTest provides the same coverage.
This this test should be enabled or removed if it adds no additional coverage.

Derby3980DeadlockTest does seem to have some testing for extendedDiagSeverity level and
diagProperties.setProperty("derby.stream.error.extendedDiagSeverityLevel", "30000");

One thing to note is that it now, with the IBM JVM, I think correctly will print
JVMDUMP010I Java dump written to ...

I am surprised though not to see a thread dump in derby.log, so maybe there is an issue with extendedDiagSeverity that needs to be looked at too.

Issue Links

• is related to: DERBY-3980 Conflicting select then update with REPEATABLE_READ gives lock timeout instead of deadlock