Hi Knut,

We are using Derby 10.1. I posted this note to the Derby Dev thread as
well. I will let you know if I hear anything from them.

Thanks,
Kal

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 09, 2008 3:10 AM
To: Derby Discussion
Subject: Re: SQLException: Restore of a serializable or SQLData object
of class , attempted to read more data than was originally stored

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(UnknownSou
rce)
>>
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>(UnknownS
ource)
>>
org.apache.derby.impl.store.raw.data.StoredPage.readRecordFromArray(Unkn
own Source)
>>
org.apache.derby.impl.store.raw.data.StoredPage.restoreRecordFromSlot(Un
known Source)
>>
org.apache.derby.impl.store.raw.data.BasePage.fetchFromSlot(UnknownSourc
e)
>
> 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


---------------------------------------------------------------------------------------------------------
This e-mail message may contain privileged and/or confidential information, and 
is intended to be received only by persons entitled to receive such 
information. If you have received this e-mail in error, please notify the 
sender immediately. Please delete it and all attachments from any servers, hard 
drives or any other media. Other use of this e-mail by you is strictly 
prohibited.


All e-mails and attachments sent and received are subject to monitoring, 
reading and archival by Monsanto, including its subsidiaries. The recipient of 
this e-mail is solely responsible for checking for the presence of "Viruses" or 
other "Malware". Monsanto, along with its subsidiaries, accepts no liability 
for any damage caused by any such code transmitted by or accompanying this 
e-mail or any attachment.
---------------------------------------------------------------------------------------------------------

Reply via email to