You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2010/03/29 18:24:27 UTC
[jira] Updated: (DERBY-4585) IndexChanger.doDelete throws
NullPointerException
[ https://issues.apache.org/jira/browse/DERBY-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-4585:
--------------------------------------
Attachment: repro.zip
The attached zip file (repro.zip) contains scripts that reproduce the NullPointerException on a fresh database. While trimming the data set, the statistics changed and so did the execution plan, so I needed to add an optimizer override in order to force the optimizer to pick a plan that failed. To reproduce, unzip the attached file and run the following command in the directory where it was unzipped:
$ java -jar /path/to/derbyrun.jar ij repro.sql
ij version 10.6
.
.
.
ij> delete from t4 where d in
(select id from t2 --derby-properties constraint=fk_t2_t1
where b in (select t1.id from t1, t3 where t1.a=t3.id and t3.c='93A720B90BB6C25703701E67D0DA75220B7D2FFC'));
ERROR XJ001: Java exception: ': java.lang.NullPointerException'.
> IndexChanger.doDelete throws NullPointerException
> -------------------------------------------------
>
> Key: DERBY-4585
> URL: https://issues.apache.org/jira/browse/DERBY-4585
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.5.3.0
> Environment: Various operating systems, Java 1.6.0_18
> Reporter: Martin Keller
> Attachments: derby-4585.tar.gz, repro.zip
>
>
> After a bunch of DELETE and DROP-Commands, the following error occurs in our application:
> 2010-03-16 12:54:23.070 GMT Thread[DRDAConnThread_4,5,derby.daemons] (XID = 15898), (SESSIONID = 1), (DATABASE = ixintrexx), (DRDAID = NF000001.PAA8-4469821361421447518{2}), Cleanup action starting
> 2010-03-16 12:54:23.070 GMT Thread[DRDAConnThread_4,5,derby.daemons] (XID = 15898), (SESSIONID = 1), (DATABASE = ixintrexx), (DRDAID = NF000001.PAA8-4469821361421447518{2}), Failed Statement is: DELETE FROM LCAPPCHILDCONTROLTITLE WHERE STRCHILDCONTROLGUID IN (SELECT STRGUID FROM LCAPPCHILDCONTROL WHERE STRAPPCONTROLDRGUID IN (SELECT A.STRGUID FROM LCAPPCONTROLDR A, LCAPPFUP B WHERE A.STRAPPFUPGUID = B.STRGUID AND B.STRAPPGUID = '93A720B90BB6C25703701E67D0DA75220B7D2FFC'))
> java.lang.NullPointerException
> at org.apache.derby.impl.sql.execute.IndexChanger.doDelete(IndexChanger.java:369)
> at org.apache.derby.impl.sql.execute.IndexChanger.delete(IndexChanger.java:544)
> at org.apache.derby.impl.sql.execute.IndexSetChanger.delete(IndexSetChanger.java:250)
> at org.apache.derby.impl.sql.execute.RowChangerImpl.deleteRow(RowChangerImpl.java:476)
> at org.apache.derby.impl.sql.execute.DeleteResultSet.collectAffectedRows(DeleteResultSet.java:405)
> at org.apache.derby.impl.sql.execute.DeleteResultSet.open(DeleteResultSet.java:137)
> at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(GenericPreparedStatement.java:416)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:297)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1235)
> at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:625)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(EmbedStatement.java:175)
> at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLIMM(DRDAConnThread.java:5022)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:750)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:290)
> Cleanup action completed
> The database seems to be corrupt, after this exception has been thrown.
> As you can see, I already compiled Derby to get the line number where the error occurs. I must apologize for not having a sufficient test case yet, but the code leading to this issue is very complex. If one wants to reproduce this bug, I can send a download link for our product and instructions to reproduce the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.