db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
Date Thu, 12 Jun 2008 00:36:45 GMT

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

Mike Matrigali updated DERBY-3607:
----------------------------------


my understanding is that the june 8 derby.log represents a complete derby.log starting with
newly created databases
using the  10.4.1.3 derby release.    I also assume you can't post the database, or a reproducible
case.  
If the above is true then the following reading of the derby.log shows:

It looks like you boot into 2 different databases.  And then there are 4 stacks from failed
checkpoints as part of shutdowns
caused by a call from outside of derby coming in.  The checkpoints are failing from:
java.nio.channels.ClosedChannelException^M
    at sun.nio.ch.FileChannelImpl.ensureOpen(Unknown Source)^M
    at sun.nio.ch.FileChannelImpl.read(Unknown Source)^M

which I think we have seen from threads getting interrupts sent at them.  Unfortunately derby
does not log what db the shutdown failures are associated with, nor useful info on what container
it is failing on.  

But none of this should cause the subsequent issues, but maybe it is related.  Can you run
the repro again from scratch (ie. creating new dbs again) and post a new derby.log so we can
see if same sequence shows up?

When the system reboots an ArrayOutOfBounds exception comes while reading a containerheader,
leading me to believe that the container header field that holds the borrowed space amount
has been corrupted.:

java.lang.ArrayIndexOutOfBoundsException^M
    at java.lang.System.arraycopy(Native Method)^M
    at org.apache.derby.impl.store.raw.data.AllocPage.ReadContainerInfo(Unknown
Source)^M
    at org.apache.derby.impl.store.raw.data.FileContainer.readHeader(Unknown Sou
rce)^M


Question is if the failed checkpoints somehow led to the corrupted container header.  

> Invalid checksum error in Derby 10.3.2.1
> ----------------------------------------
>
>                 Key: DERBY-3607
>                 URL: https://issues.apache.org/jira/browse/DERBY-3607
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.2.1, 10.4.1.3
>         Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate
3.1.1.RC3,c3p0
>            Reporter: Shahbaz
>            Priority: Critical
>         Attachments: derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml
>
>
> I am getting this execption when ever I try to restart my application
> java.sql.SQLException: Invalid checksum on Page Page(0,Container(0, 2033)), expected=2,731,401,932,
on-disk version=2,375,776,513, page dump follows: Hex dump:
> 00000000: 0076 0000 0001 0000 0000 0000 0002 0000  .v..............
> 00000010: 0000 0006 0000 0000 0000 0000 0000 0000  ................
> 00000020: 0000 0000 0001 0000 0000 0000 0000 0000  ................
> 00000030: 0000 0000 0000 0000 0000 0000 ffff ffff  ................
> 00000040: ffff ffff 0000 0000 0000 0000 0000 0000  ................
> 00000050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
> 00000060: 0000 0000 0000 0000 0000 0000 5000 0000  ............P...
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
> 	at com.mchange.v2.c3p0.impl.NewProxyCallableStatement.execute(NewProxyCallableStatement.java:3044)
> 	at ae.sphere.arena.database.management.backup.BackupStategy.createBackup(BackupStategy.java:56)
> 	at ae.sphere.arena.database.management.backup.BackupStategy.doSchedulerJob(BackupStategy.java:41)
> 	at ae.sphere.arena.common.jobscheduler.Scheduler$1.run(Scheduler.java:49)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> 00000070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
> 00000080: 0000 0000 0000 0000 0000 0000 0000 0000  ................
> 00000090: 0000 0000 0000 0000 0000 0000 0000 0000  ................
> 000000a0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
> 000000b0: 0000 0

-- 
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