[DERBY-2808] triggerRecursion.sql and triggerGeneral.sql intermittently fail with SAVEPOINT error.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 10.2.2.1, 10.3.1.4
• Fix Version/s: 10.3.2.1, 10.4.1.3
• Component/s: Test
• Bug behavior facts: Regression Test Failure
• Assignee: Unassigned
• Reporter: A B
• Created: 12/Jun/07 22:12
• Updated: 05/May/10 11:13
• Resolved: 06/Feb/08 16:45

Description

I saw triggerRecursion.sql fail once against 10.2 trunk with svn # 545682. The diff was:

• • • Start: triggerRecursion jdk1.5.0 derbyall:derbylang 2007-06-12 00:24:49 ***
      92 del
      < ERROR 54038: Maximum depth of nested triggers was exceeded.
      92a92
      > ERROR 3B501: A SAVEPOINT with the passed name already exists in the current transaction.
      Test Failed.

This SAVEPOINT error is the same as the one shown in DERBY-1457, but the full diff is not the same as for that Jira, so I'm filing a separate issue. The two could be related, though.

Also note: triggerGeneral.sql failed against the 10.3 trunk on the same day with the same kind of diff:

• • • Start: triggerGeneral jdk1.5.0 derbyall:derbylang 2007-06-11 22:24:00 ***
      939 del
      < ERROR 54038: Maximum depth of nested triggers was exceeded.
      939a939
      > ERROR 3B501: A SAVEPOINT with the passed name already exists in the current transaction.
      Test Failed.

Again, might be related to DERBY-1457, might not be.

Both failures were seen with ibm15.

Issue Links

• is duplicated by: DERBY-1457 lang/triggerGeneral.sql fails intermittently
• is related to: DERBY-2773 testGrantRevokeDDL(org.apache.derbyTesting.functionTests.tests.lang.GrantRevokeDDLTest) throws java.sql.SQLException: The exception 'java.sql.SQLException: A SAVEPOINT with the passed name already exists in the current transaction.'
• relates to: DERBY-3093 Intermittent transaction failure caused by internal duplicate savepoint name for triggers