The info you asked for. Yes, I can probably strip down a test version, but will take a little while. Note I'm running this in WSAD 5.0.1 and its using the JRE 1.3.x I've setup an ANT script to run outside of eclipse(WSAD) and it appears I'm not getting this error, I have some other ANT/Junit problems that I'm working through, but I appear to be able to run those tests through multiple times and its ok. I have the ant script running against JDK1.4.2
So, it's looking like a conflict between Derby and WSAD5.0.1 Java Version: 1.4.2 Java Vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\j2re1.4.2 Java classpath: C:\Program Files\IBM\IBM CICS Transaction Gateway\Classes\CTGCL IENT.JAR;C:\Program Files\IBM\IBM CICS Transaction Gateway\Classes\CTGSERVER.JAR ;C:\Program Files\IBM\IBM CICS Transaction Gateway\Classes\CICSJ2EE.JAR;C:\Progr am Files\IBM\IBM CICS Transaction Gateway\Classes\CTGSAMPLES.JAR;C:\Program File s\IBM\Cloudscape_10.0\lib\db2jcc.jar;C:\Program Files\IBM\Cloudscape_10.0\lib\db 2jcc_license_c.jar;C:\Program Files\IBM\Cloudscape_10.0\lib\derby.jar;C:\Program Files\IBM\Cloudscape_10.0\lib\derbynet.jar;C:\Program Files\IBM\Cloudscape_10.0 \lib\derbytools.jar;C:\Program Files\IBM\WebSphere Studio\eclipse\plugins\apache -ant-1.6.5\lib\*.jar OS name: Windows XP OS architecture: x86 OS version: 5.1 --------- Derby Information -------- [C:\Program Files\IBM\Cloudscape_10.0\lib\db2jcc.jar] 2.4 - (17) [C:\Program Files\IBM\Cloudscape_10.0\lib\db2jcc_license_c.jar] 2.4 - (17) [C:\Program Files\IBM\Cloudscape_10.0\lib\derby.jar] 10.0.2.2 - (165169) [C:\Program Files\IBM\Cloudscape_10.0\lib\derbynet.jar] 10.0.2.2 - (165169) [C:\Program Files\IBM\Cloudscape_10.0\lib\derbytools.jar] 10.0.2.2 - (165169) ------------------------------------------------------ ----------------- Locale Information ----------------- ------------------------------------------------------ -----Original Message----- From: Suresh Thalamati [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 16, 2005 4:57 PM To: Derby Discussion Subject: Re: Error when running a delete all a 2nd time The stack in derby.log is interesting , I do see a run() method in RafContainer.java. 1) Are u running under security manager ? 2) What JVM & OS are u using ? 3) Are u able to reproduce this problem with a simple set of SQL statements not the whole application ? Could u please post the output of the following command : java org.apache.derby.tools.sysinfo Thanks -suresht Peart, David E. wrote: > find attached the derby.log I don't know if this will offer any > additional insight. > > ---------------------------------------------------------------------- > -- > *From:* Satheesh Bandaram [mailto:[EMAIL PROTECTED] > *Sent:* Tuesday, August 16, 2005 1:19 PM > *To:* Derby Discussion > *Subject:* Re: Error when running a delete all a 2nd time > > I think Army has already answered this question...Since there is a > primary key on the column, Derby would have created an unique index on > it, so attempting to create another unique index on the same column > would raise the warning. Why it is a warning and not an error, I don't > know :-) (since it doesn't actually create the second index...) > > So your first problem is not related to this one... > > Satheesh > > Peart, David E. wrote: > >> Satheesh >> >> when you say a complete reproduction you mean all code, etc? >> >> Anyway, I'm also getting this error on creating indexes, may be it is >> related. So I'd like to see if this was resolved then see if the >> other problem goes away. >> The problem is: >> >> WARNING 01504: The new index is a duplicate of an existing index: >> SQL050816084652910. >> >> But its not a duplicate. It creates this warning on the 2nd index >> PARGRP.X2FTNRC2 >> Additionally, although its a warning it does not create the 2nd index >> !!!!! I checked the system tables for which indexes are created. >> Let me know if you need the ddl on the table again, and may be you >> can try creating the table with the three indexes and see if you get >> the same error. >> Note: we are loading the tables onto DB2 and have no issues there. >> >> Here is the ddl script for creating the indexes >> >> CREATE UNIQUE >> INDEX PARGRP.X1FTNRC2 >> ON PARGRP.FTNREC2_CATCTRL >> (CARRIER_CD ASC >> ,TARIFF_CD ASC >> ,FOOTNOTE_CD ASC >> ,CATEGORY_NO ASC >> ,SEQUENCE_NO ASC >> ,CREATE_TS ASC >> ); >> >> CREATE UNIQUE >> INDEX PARGRP.X2FTNRC2 >> ON PARGRP.FTNREC2_CATCTRL >> (FTNREC2_SG ASC >> ); >> >> CREATE >> INDEX PARGRP.X3FTNRC2 >> ON PARGRP.FTNREC2_CATCTRL >> (BATCH_CI ASC >> ,BATCH_NO ASC >> ); >> >> David >> >> --------------------------------------------------------------------- >> --- >> *From:* Satheesh Bandaram [mailto:[EMAIL PROTECTED] >> *Sent:* Friday, August 12, 2005 3:20 PM >> *To:* Derby Discussion >> *Subject:* Re: Error when running a delete all a 2nd time >> >> Hi Peart, >> >> The error is really strange... I can't spot what could be causing the >> problem here. Would it be possible for you to make a complete >> reproduction? >> >> Satheesh >> >> Peart, David E. wrote: >> >>> I'm getting the following internalError when I try and delete from a >>> table after I have populated it. Has anybody seen this error or >>> know whats causing it. It only happens with this table (find the >>> ddl attached), other tables are fine I've using this to do some TDD. >>> a) So I delete the contents of the table in a class setup >>> b) load the data >>> c) after all tests have run, delete the contents of the table >>> >>> It's during the 'c' step this occurs, and after I get this any >>> attempt to delete from the table produces this error. >>> >>> Any help would be appreciated as this is driving me crazy. >>> >>> MessageID = "XJ001.U" >>> SQLState = "XJ001" >>> >>> net.atpco.common.dataaccess.errors.DataAccessApplicationException: >>> unexpected error occurred in attempt to execute SQL: Java exception: >>> 'No run method: java.lang.InternalError'.; Caused by --> >>> java.lang.InternalError: No run method at >>> org.apache.derby.impl.sql.execute.DeleteCascadeResultSet.open(Delete >>> CascadeResultSet.java) >>> at >>> org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPr >>> eparedStatement.java) >>> at >>> org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStat >>> ement.java) >>> at >>> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(E >>> mbedPreparedStatement.java) >>> at >>> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Embe >>> dPreparedStatement.java) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.MockJDBCDAO.createUpdate >>> Delete(MockJDBCDAO.java:393) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.MockJDBCDAO.delete(MockJ >>> DBCDAO.java:442) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.FootNotesJDBCDAOFake.del >>> ete(FootNotesJDBCDAOFake.java:93) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.GenericFootNotesJDBCDAO. >>> delete(GenericFootNotesJDBCDAO.java:208) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.GenericFootNotesDaSvc.de >>> lete(GenericFootNotesDaSvc.java:148) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.GenericFootNotesDaSvc.de >>> lete(GenericFootNotesDaSvc.java:152) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.FootNotesDaSvcTest.delet >>> eSeedData(FootNotesDaSvcTest.java:207) >>> at >>> net.atpco.rules.footnotes.server.dataaccess.FootNotesDaSvcTest$1.set >>> Up(FootNotesDaSvcTest.java:41) at >>> junit.extensions.TestSetup$1.protect(TestSetup.java:18) >>> at junit.framework.TestResult.runProtected(TestResult.java:124) >>> at junit.extensions.TestSetup.run(TestSetup.java:23) >>> at >>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remo >>> teTestRunner.java:329) >>> at >>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTes >>> tRunner.java:218) >>> at >>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTe >>> stRunner.java:151) >>> at >>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTe >>> stRunner.java:151) >>> >>>
