Bryan Pendleton <[EMAIL PROTECTED]> writes: > INUGANTI, KALYAN [AG-Contractor/1000] wrote: >> here are the 2 stack-traces that were in the derby.log. > ... >> 2008-01-08 17:28:27.478 GMT Thread[main,6,main] (XID = 4008637), >> (SESSIONID = 0), (DATABASE = B:\SeedTrakDB), (DRDAID = null), Failed >> Statement is: select * from productorder >> java.lang.ArrayIndexOutOfBoundsException: -1 >> org.apache.derby.impl.store.raw.data.BasePage.getHeaderAtSlot(UnknownSource) >> org.apache.derby.impl.store.raw.data.StoredPage.restorePortionLongColumn(Unknown >> Source) >> org.apache.derby.impl.store.raw.data.OverflowInputStream.fillByteHolder(Unknown >> Source) >> org.apache.derby.impl.store.raw.data.OverflowInputStream.<init>(UnknownSource) >> org.apache.derby.impl.store.raw.data.StoredPage.readRecordFromArray(Unknown >> Source) >> org.apache.derby.impl.store.raw.data.StoredPage.restoreRecordFromSlot(Unknown >> Source) >> org.apache.derby.impl.store.raw.data.BasePage.fetchFromSlot(UnknownSource) > > Unfortunately, this looks like evidence of a damaged/corrupt database.
What I find a bit worrying is that we have seen similar corruptions (at least the stack traces are similar) in the regression tests lately: https://issues.apache.org/jira/browse/DERBY-3287 https://issues.apache.org/jira/browse/DERBY-3292 Kal, could you tell us which version of Derby you are using? -- Knut Anders
