[jira] Created: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 - 3 - 4 | Next > |
 |
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shahbaz updated DERBY-3607: --------------------------- Attachment: derby.log Deby logs with 10.4.3.1 > 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604215#action_12604215 ] Shahbaz commented on DERBY-3607: -------------------------------- We migrated to 10.4.3.1, still the same problem but with new exception ERROR XSDG3: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@1386d2b could not be accessed at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer.clean(Unknown Source) at org.apache.derby.impl.services.cache.ConcurrentCache.cleanAndUnkeepEntry(Unknown Source) We are getting the same in embedded mode and DB is newly created. > 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604227#action_12604227 ] Bassel Kh commented on DERBY-3607: ---------------------------------- It is very strange of having these kinds of bugs with such a professional db like Derby. Anyways, the error has changed after using Derby 10.4: 2008-06-11 10:50:37.997 GMT Thread[Worker-60,5,main] (XID = 825230855), (SESSIONID = 29), (DATABASE = db/networkManager), (DRDAID = null), Cleanup action starting 2008-06-11 10:50:37.997 GMT Thread[Worker-60,5,main] (XID = 825230855), (SESSIONID = 29), (DATABASE = db/networkManager), (DRDAID = null), Failed Statement is: select monitor.status as status , count(monitor.status) as statusCount , sum (monitor.metthresholdtimes) as thresholdTimes from NetworkManager.ACTIVE_MONITOR as monitor where monitor.col1 <> 'Yes' group by monitor.status java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at org.apache.derby.impl.store.raw.data.AllocPage.ReadContainerInfo(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.readHeader(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at org.apache.derby.impl.store.raw.data.RAFContainer.openContainer(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.setIdent(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer.setIdentity(Unknown Source) at org.apache.derby.impl.services.cache.ConcurrentCache.find(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source) at org.apache.derby.impl.store.raw.xact.Xact.openContainer(Unknown Source) at org.apache.derby.impl.store.access.btree.index.B2IFactory.readConglomerate(Unknown Source) at org.apache.derby.impl.store.access.RAMAccessManager.conglomCacheFind(Unknown Source) at org.apache.derby.impl.store.access.RAMTransaction.findExistingConglomerate(Unknown Source) at org.apache.derby.impl.store.access.RAMTransaction.openStoreCost(Unknown Source) at org.apache.derby.impl.sql.compile.CompilerContextImpl.getStoreCostController(Unknown Source) at org.apache.derby.impl.sql.compile.FromBaseTable.getStoreCostController(Unknown Source) at org.apache.derby.impl.sql.compile.FromBaseTable.estimateCost(Unknown Source) at org.apache.derby.impl.sql.compile.OptimizerImpl.estimateTotalCost(Unknown Source) at org.apache.derby.impl.sql.compile.OptimizerImpl.costBasedCostOptimizable(Unknown Source) at org.apache.derby.impl.sql.compile.OptimizerImpl.costOptimizable(Unknown Source) at org.apache.derby.impl.sql.compile.FromBaseTable.optimizeIt(Unknown Source) at org.apache.derby.impl.sql.compile.ProjectRestrictNode.optimizeIt(Unknown Source) at org.apache.derby.impl.sql.compile.OptimizerImpl.costPermutation(Unknown Source) at org.apache.derby.impl.sql.compile.SelectNode.optimize(Unknown Source) at org.apache.derby.impl.sql.compile.DMLStatementNode.optimizeStatement(Unknown Source) at org.apache.derby.impl.sql.compile.CursorNode.optimizeStatement(Unknown Source) at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown Source) at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown Source) at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(Unknown Source) at org.apache.derby.jdbc.Driver30.newEmbedPreparedStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:442) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:368) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:105) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561) at org.hibernate.loader.Loader.doQuery(Loader.java:661) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223) at org.hibernate.loader.Loader.doList(Loader.java:2147) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2026) at org.hibernate.loader.Loader.list(Loader.java:2021) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:109) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1475) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:121) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:168) ----------------------------------- > 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604437#action_12604437 ] Shahbaz commented on DERBY-3607: -------------------------------- Just want to add that the DB is 10.3 generated, sorry forgot to mention earlier. Now we are trying to migrate the data into 10.4 DB. > 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shahbaz updated DERBY-3607: --------------------------- Attachment: DB_10.4logs.zip Hi, Please find the logs of the same issue using 10.4 generated DB. Two DBs running in embedded mode. > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Issue Comment Edited: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604212#action_12604212 ] shahbaz edited comment on DERBY-3607 at 6/12/08 5:45 AM: --------------------------------------------------------- Deby logs with 10.4.1.3 was (Author: shahbaz): Deby logs with 10.4.3.1 > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Issue Comment Edited: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604215#action_12604215 ] shahbaz edited comment on DERBY-3607 at 6/12/08 5:47 AM: --------------------------------------------------------- We migrated to 10.4.1.3, still the same problem but with new exception ERROR XSDG3: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@1386d2b could not be accessed at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer.clean(Unknown Source) at org.apache.derby.impl.services.cache.ConcurrentCache.cleanAndUnkeepEntry(Unknown Source) We are getting the same in embedded mode and DB is newly created. was (Author: shahbaz): We migrated to 10.4.3.1, still the same problem but with new exception ERROR XSDG3: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@1386d2b could not be accessed at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.store.raw.data.RAFContainer.clean(Unknown Source) at org.apache.derby.impl.services.cache.ConcurrentCache.cleanAndUnkeepEntry(Unknown Source) We are getting the same in embedded mode and DB is newly created. > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3607: ---------------------------------- Just to verify, is it true that the 6/11 zip's - DB_10.4logs.zip represent running your application on 10.4 and creating the databases in 10.4. Do the log's represent the entire run of the test? This derby.log did not have the checkpoint errors so if this is the complete run that can probably be eliminated. The subsequent error looks the same as the previous postings - ie. there is some corruption in the first page of an index on the Does your app have the ability to run with just one database? And if so can you reproduce this problem with just one database - I am just trying to narrow down the cause. The latest is showing corruptions in 1st page of at least 2 indexes (but hard to say exactly what without the db, if there are views involved then could be same table). 1st: index on Arena.USERS 2nd: index on Arena.NOTIFICATION_SCHEDULER No other errors in the logs. There are a number of startups and shutdowns. Could you describe how you shutdown the databases? > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3607: ---------------------------------- just to eliminate another code path - your databases are not encrypted, right? > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3607: ---------------------------------- another code path question, during the repro do you back up the database? > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604808#action_12604808 ] Shahbaz commented on DERBY-3607: -------------------------------- 1. Yes DB_10.4logs.zip is complete 10.4 (DB and application) 2. We actualy have 3 dbs, and in this case we were able to repro this problem quickly, so we made the 2 dbs and the above case happened with that only, although not as frequently. As of now we cant have 1 db. 3. This problem comes only when we do shutdown and startups, so while testing we have to do the same multiple times. We are running our servers as services, so we just start and stop the service to repro the same. 4. For shut down, we have added this on jvm hook, in that we do following things a. get all DBs b. close all current sessions, and seesion factories (hibernate level) for each db c. finally Derby shutdown using following method, for all dbs public boolean shutdownDB(){ try { Bundle b = Platform.getBundle("ae.sphere.arena.database.common"); b.loadClass("org.apache.derby.jdbc.EmbeddedDriver").newInstance(); DriverManager.getConnection("jdbc:derby:;shutdown=true", "xxx", "xxxx"); return false; } catch (ClassNotFoundException e) { LOG.error(e); } catch (SQLException e) { if (e.getSQLState()!= null && (e.getSQLState().equals("08006") || (e.getSQLState().equals("XJ015")))) { LOG.error("it is not error, shutdown successfully ;"+e.getMessage()); return true; }else{ LOG.error(e); } } catch (InstantiationException e) { LOG.error(e); } catch (IllegalAccessException e) { LOG.error(e); } return false; } 5. Databases are not encrypted but encrypted data we push. 6. We have "online" backup and its always on, depends on the schedule set by user. 7. We tried to prepare the sample for you to reproduce, but while testing we couldnt get the corruption, so no point of senditng it to you, however with full application it is easier to repro the same. Will corrupted DB help you, if yes where and how we can send you, as the db size is big. > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3607: ---------------------------------- Thanks for the info, without a repro I have been inspecting the code and anything that you can tell me about the app helps direct that effort. Of course if you can come up with a repro that could be run it is much more likely someone will be able to find the issue. If you can't give a repro I am going to continue to ask questions about the app in your environment, and maybe something will come of that. How big is a zipped copy of the db? Getting a copy of it may help as it would be interesting to look at the state of page 0 in the 2 corrupted tables. jira will allow up to 10mb of a zipped attachment. there may be other places at a apache we could load a bigger file, just not sure right now. depending on when you enabled online backup the log may include a complete update history of the db and looking at it or more likely comparing it with a few other examples of the bug may lead to what kinds of things lead to the problem. My current assumption is that the problem is caused by some I/O interaction similar to DERBY-3347. Could you describe the concurrency in the simplest case that you have been able to reproduce this problem. Basically how many threads are involved and do they run concurrently? Things like are the startup/shutdown of the 2 db's done independently on different threads? While running how many threads/connections are done doing work in the 2 db's. Can you describe when and how often you execute the command that "enables" online backup? It is at this point that derby copies a number of database files from the original db to your backup location and it does have some code that insures that the page 0 is up to date before the copy. Is it possible to run your test without online backup ever being called just to see it the bug still reproduces? You mentioned "jvm hook", does this mean you are also shutting down the jvm durring the test run? If so can you describe how often, ie. for every shutdown in the derby.log is there also a jvm shutdown? I think this is what you mean by your services comment. Is the following what is going on: o You start a service and what it does is start up a jvm, it opens the 2 databases, and some set of work is somehow done in both the db's (is this work different or the same for each try). Then you stop the service sometime later which shuts down the jvm and as part of jvm hooks your specific shutdown stuff happens. How are clients shutdown? Is it possible that in progress clients are shutdown by "killing" them somehow? I am not familar with hibernate so this could be a part of "the seesion factories (hibernate level) shutdown" ? Is any of the work that is done during the tests include deletes, updates to fields included in any index/contraint, or inserts which fail due to duplicate key errors, ddl after the initial create of the database? This is interesting as it may queue background work to reclaim deleted space and thus add another point of concurrency to the work being done. Does each startup/shutdown phase always access the same tables, looking to verify that when you get an error on a particular table whether it is guaranteed that the table was working in the previous startup/shutdown test phase. Another thing I am looking at is a possiblity that exaustion of resources is coming into play, which would explain why it takes multiple db's. Do you set any derby properties as part of your application, if so could you post all the ones that you change. Can you estimate about how many different derby tables might be accessed during one of the startup/shutdown phases of your test? I know this is hard as it should also include how many indexes may be referenced. The 2 resources I am mostly thinking about are the page cache and the open container cache. The page cache defaults to 1000 and the open container cache defaults to 100. Depending on your application (basically concurrent user threads and the background thread used for post commit and checkpoints) we may have multiple open "channels" on each container in the open container cache - i am not exactly sure what resource this maps to on windows. > 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: DB_10.4logs.zip, 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shahbaz updated DERBY-3607: --------------------------- Attachment: SingleThread Test.zip Oops, we tried to create single thread test, making sure that at any point only one thread is active, still we found same issue, using 10.4. > 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: DB_10.4logs.zip, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, SingleThread Test.zip > > > 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604961#action_12604961 ] Shahbaz commented on DERBY-3607: -------------------------------- 1. Default online backup is daily, but I dont think that it is running at the same time of corruption, as timings are completely different, but we will do the test and let you know. 2. You are right in getting the shutdown and start up processes. What do you mean by "clients"?. Using hibernate, we are closing all the connections and all, befor derby shutdown. 3. Shutdown/Startup process is consistant. 4. Derby properties System.setProperty("derby.stream.error.file", "logs/derby.log"); System.setProperty("derby.stream.error.logSeverityLevel", "0"); System.setProperty("derby.locks.monitor","true"); System.setProperty("derby.locks.deadlockTrace","true"); System.setProperty("derby.locks.deadlockTimeout","20"); > 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: DB_10.4logs.zip, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, SingleThread Test.zip > > > 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3607: ---------------------------------- what hardware are you running the test on? Mostly I am looking for number of cpu's and number of cores on the cpu's to again understand the possible concurrency going on. Thanks for running the single thread test, I will look at it. Even if from your app point of view it is single threaded, derby may use multiple threads per db to take care of background things like checkpoint and delete row processing. That is why I wanted to know a little more about the actions your app takes when reproducing the problem. > 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: DB_10.4logs.zip, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, SingleThread Test.zip > > > 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604974#action_12604974 ] Shahbaz commented on DERBY-3607: -------------------------------- Its Intel Core 2 CPU 6300, 1.8 GHz, with Win XP SP2. We are mostly updating the rows very frequently. Deleting is not that frequent but update/Insert/select is very frequent. and at the time of service restarts also the transactions must be on. > 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: DB_10.4logs.zip, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, SingleThread Test.zip > > > 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. |
|
|
[jira] Updated: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3607: ---------------------------------- if you can't come up with a repro, are you able to build/debug/run derby itself. The following suggestion would help identify if nio is still the problem: One thing I know was changed in that area of the code in that period, is that RAFContainer started using java.nio.* to allow parallel reads and writes on JVMs that support nio. It is possible to force the use of the old mechanism by deleting or commenting out the following lines in java/engine/org/apache/derby/modules.properties and rebuilding derby.jar: # store data using a StorageFactory # Enhanced version using NIO API; requires Java 1.4 derby.module.rawStore.data.genericJ4=org.apache.derby.impl.store.raw.data.BaseDataFileFactoryJ4 derby.env.jdk.rawStore.data.genericJ4=4 derby.env.classes.rawStore.data.genericJ4=java.nio.Buffer cloudscape.config.rawStore.data.genericJ4=derby It would be great if you could make that change and rerun your test. > 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: DB_10.4logs.zip, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, SingleThread Test.zip > > > 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605054#action_12605054 ] Shahbaz commented on DERBY-3607: -------------------------------- For your information, we are using Java 1.5 and 1.6. Is there any expected problem using the same? > 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: DB_10.4logs.zip, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, SingleThread Test.zip > > > 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. |
|
|
[jira] Commented: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
[ https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605138#action_12605138 ] Shahbaz commented on DERBY-3607: -------------------------------- We will do the same test and let you know, but we couldnt find "cloudscape.config.rawStore.data.genericJ4" property in module.properties in derby.jar Please advise. > 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: DB_10.4logs.zip, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, SingleThread Test.zip > > > 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. |
| < Prev | 1 - 2 - 3 - 4 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
