db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1457) lang/triggerGeneral.sql fails intermittently
Date Wed, 05 May 2010 11:14:02 GMT

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

Kristian Waagan closed DERBY-1457.
----------------------------------


Closing issue.

> lang/triggerGeneral.sql fails intermittently
> --------------------------------------------
>
>                 Key: DERBY-1457
>                 URL: https://issues.apache.org/jira/browse/DERBY-1457
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.1.6, 10.3.1.4
>         Environment: - IBM wsdd5.6 j9_13
> - IBM 142:
>     java version "1.4.2_07"
>     Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05)
>     Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)
> -ibm 1.5
>            Reporter: Deepa Remesh
>            Priority: Minor
>
> This failure seems to be intermittent. The diff is:
> *** Start: triggerGeneral jdk1.3.1 subset - 2.1 derbyall:derbylang 2006-06-26 09:18:19
***
> 941 del
> < DERBY-388 Test Passed.
> 941a941,950
> > ERROR 38000: The exception 'SQL Exception: A SAVEPOINT with the passed name already
exists in the current transaction.' was thrown while evaluating an expression.
> > ERROR 3B501: A SAVEPOINT with the passed name already exists in the current transaction.
> > ij> -- Derby-85: It turns out that if a table t1 exists in a non-default schema

> > -- and the default schema (e.g., "SOMEUSER") doesn't exist yet (because no 
> > -- objects have been created in that schema), then attempts to create a 
> > -- trigger on t1 using its qualified name will lead to a null pointer 
> > -- exception in the Derby engine. 
> > connect 'wombat;user=someuser';
> > ij(CONNECTION1)> autocommit off;
> > ij(CONNECTION1)> create table myschema.mytable (i int);
> 943,951d951
> < ij> -- Derby-85: It turns out that if a table t1 exists in a non-default schema

> < -- and the default schema (e.g., "SOMEUSER") doesn't exist yet (because no 
> < -- objects have been created in that schema), then attempts to create a 
> < -- trigger on t1 using its qualified name will lead to a null pointer 
> < -- exception in the Derby engine. 
> < connect 'wombat;user=someuser';
> < ij(CONNECTION1)> autocommit off;
> < ij(CONNECTION1)> create table myschema.mytable (i int);
> < 0 rows inserted/updated/deleted
> Test Failed.
> *** End:   triggerGeneral jdk1.3.1 subset - 2.1 derbyall:derbylang 2006-06-26 09:18:52
***
> Stack trace of failure is:
> ERROR 3B501: A SAVEPOINT with the passed name already exists in the current transaction.
> 	at java.lang.Throwable.<init>(Throwable.java)
> 	at java.lang.Throwable.<init>(Throwable.java)
> 	at org.apache.derby.iapi.error.StandardException.<init>(StandardException.java:83)
> 	at org.apache.derby.iapi.error.StandardException.<init>(StandardException.java:72)
> 	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:294)
> 	at org.apache.derby.impl.store.raw.xact.Xact.setSavePoint(Xact.java:1420)
> 	at org.apache.derby.impl.store.access.RAMTransaction.setSavePoint(RAMTransaction.java:1997)
> 	at org.apache.derby.impl.sql.conn.GenericStatementContext.setSavePoint(GenericStatementContext.java:257)
> 	at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java)
> 	at org.apache.derby.impl.sql.execute.GenericTriggerExecutor.executeSPS(GenericTriggerExecutor.java)
> 	at org.apache.derby.impl.sql.execute.RowTriggerExecutor.fireTrigger(RowTriggerExecutor.java:110)
> 	at org.apache.derby.impl.sql.execute.TriggerEventActivator.notifyEvent(TriggerEventActivator.java:277)
> 	at org.apache.derby.impl.sql.execute.UpdateResultSet.fireAfterTriggers(UpdateResultSet.java:825)
> 	at org.apache.derby.impl.sql.execute.UpdateResultSet.open(UpdateResultSet.java:288)
> 	at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1181)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:584)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:516)
> 	at org.apache.derbyTesting.functionTests.tests.lang.userDefMethods.derby388(userDefMethods.java:137)
> 	at org.apache.derby.exe.ac46a08075x010cx1122x5cc3x0000187d3624a5.g0(Unknown Source)
> 	at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:199)
> 	at java.lang.reflect.Method.invoke(Method.java:252)
> 	at org.apache.derby.impl.services.reflect.ReflectMethod.invoke(ReflectMethod.java:45)
> 	at org.apache.derby.impl.sql.execute.CallStatementResultSet.open(CallStatementResultSet.java:67)
> 	at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1181)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:584)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:516)
> 	at org.apache.derby.impl.tools.ij.ij.executeImmediate(ij.java)
> 	at org.apache.derby.impl.tools.ij.utilMain.doCatch(utilMain.java:433)
> 	at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:310)
> 	at org.apache.derby.impl.tools.ij.Main.go(Main.java:207)
> 	at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:173)
> 	at org.apache.derby.impl.tools.ij.Main.main(Main.java:75)
> 	at org.apache.derby.tools.ij.main(ij.java:56)

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


Mime
View raw message