[jira] Resolved: (DERBY-2808) triggerRecursion.sql and triggerGeneral.sql intermittently fail with SAVEPOINT error.

["Kathey Marsden (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden resolved DERBY-2808.
-----------------------------------

    Resolution: Duplicate

duplicate of DERBY-3093


> triggerRecursion.sql and triggerGeneral.sql intermittently fail with SAVEPOINT error.
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-2808
>                 URL: https://issues.apache.org/jira/browse/DERBY-2808
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.2.2.1, 10.3.1.4
>            Reporter: A B
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.