[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] 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=12605223#action_12605223 ] Knut Anders Hatlen commented on DERBY-3607: ------------------------------------------- That line is only part of modules.properties in the source tree. If you modify modules.properties in derby.jar, just deleting the other properties Mike mentioned should be OK. If this is the same issue as DERBY-3606 (same reporter, same symptoms), I'd assume the NIO changes are not causing the problem, as that bug was reported against 10.2.2.0. The NIO code was introduced in 10.3.1.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] 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 After commenting the same as suggested, we found the exceptions as in attached logs. > 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, 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: ---------------------------------- Your latest run came up with a slightly different kind of error, a checksum error rather than the consistent array out of bounds from previous runs. I don't know if that is signicant or not. If you have time could you run the repro of few more times with nio disabled and post the logs - maybe give them different names to make it clear which is which. Just to see if checksum is always the error in this case. The difference is that the header info is readable in this latest case and then we check the checksum, but in previous case we can't even read the header. Given the latest problem maybe there is bad synchronization in some path of the base i/o code, and not the nio code. did you ever get a chance to turn off all backups during your repro case? Could you post the modules.properties you ran your last test with. If this did turn off nio, and it was the only one in your path then the issue is in some other part of code than I have be guessing at. Again the assumption is that each time you post results your test run starts with a new created db. I am not aware of any issues with jdk15 or jdk16 that would cause this issue. Just to be specific can you post exact jdk versions of the jvm's you are running the tests with when you post your results. For instance is it the sun jdk16? java -version will give you the output i am interested in. I don't really think the jvm is the issue. you could try latest test case, in each instance creating new db's for each test run agains jdk14, jdk15, and jdk16 to make sure. > 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, 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: ---------------------------------- After the first startup/shutdown phase, does your reproduction test create tables in the subsequent startup/shutdowns? > 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, 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 ] Shahbaz updated DERBY-3607: --------------------------- Attachment: modules.properties Online backup is not working at the time of corruption. We are using Java 1.5 from last some tests. Can we send you whole application installers with DB to reproduce the same at your end. As it will be quicker? Attach are modules.property file. Everytime we are not generating new db, for example for this changes in properties tests, we used our 10.4 generated db and performed test. Is it cruicial to generate the same everytime, as I dont think these changes should have any affect on 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, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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 create the db and then use a copy of it for each iteration then that is ok. The nature of the corruption is that once it happens it will not get fixed, so if you use a broken one for the next test, the test does not tell us anything. My assumption of what is happening is that the page actually gets corrupted before it gets recognized. This may be happening one or more complete startup/shutdown phases before it actually gets noticed. I didn't completely understand your answer about online backup. Was an online backup ever taken during the reproduction, anytime from starting with the fresh db until the corruption happens. It is not clear to me your application knows exactly when the corruption happens. You still have not described what work is done in each startup/shutdown phase. If it is exactly the same work then it is likely it does know. But if there is some random/test work it may be that you don't see the page in one iteration. You could run a consistency check in between each phase to definitely tell when the corruption happens. The best case would be to attach the application/db to this jira for anyone to reproduce. What is the zipped size of the jars and 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: DB_10.4logs.zip, derby.log, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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=12605694#action_12605694 ] Shahbaz commented on DERBY-3607: -------------------------------- 1. Corrupted DB can not be used in any case, so we are using fresh db but once generated. 2. Online back up component is on but it never happened, DB gets corrupted before back up. so it never happened during tests. 3. Shutdown process, I already explained in previous posts and startup is simple, we just start the dbs, start the connections and start the normal work for application. We do the same work to reproduce the same, the only difference is that some times it appears quickly and some times it needs some 6-7 restarts. Our application doesn't know when its corrupted, but as user we can know with functionality failures and logs. Corrupted tables are not consistent meaning some times some tables and some times another tables. 4. Do you want to say that corruption happens during running of application? 5. I can send you application exe with DB, which is around 200 MB, as sample is not able to corrupt the same. for the same we can create one ftp account for you guys to download and test from their. > 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, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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: ---------------------------------- > 1. Corrupted DB can not be used in any case, so we are using fresh db but once generated. great, that is fine. > 2. Online back up component is on but it never happened, DB gets corrupted bef ore back up. so it never happened during tests. ok, now I won't worry about looking at the online backup code. > 3. Shutdown process, I already explained in previous posts and startup is simp le, we just start the dbs, start the connections and start the normal work for a pplication. We do the same work to reproduce the same, the only difference is th at some times it appears quickly and some times it needs some 6-7 restarts. Our application doesn't know when its corrupted, but as user we can know with functi onality failures and logs. Corrupted tables are not consistent meaning some time s some tables and some times another tables. > 4. Do you want to say that corruption happens during running of application? It is all a guess at this point. But often with these types a problems the corruption happens at an earlier time either as part of the application or part of a previous shutdown. This problem has the feel of the page being fine in the buffer cache, but somehow being corrupted as it is being written out. Because of the cache the application may run just fine accessing the "corrupted on disk page" because the good copy is still in cache. > 5. I can send you application exe with DB, which is around 200 MB, as sample i s not able to corrupt the same. for the same we can create one ftp account for y ou guys to download and test from their. if you can set up a download site and instructions on how to reproduce, seems much more likely someone will be able to figure out what is going on. If the 200mb example does not reproduce the issue then that does not seem helpful. Go ahead and set up ftp of case that reproduces the problem, along with details on how to reproduce. > 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, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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: ---------------------------------- could you remove the db shutdown hook and see if you can reproduce the bug. Is it possible that the shutdown hook is running in a different class loader from the class loader that started the db/connects to the 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: DB_10.4logs.zip, derby.log, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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] 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=12605786#action_12605786 ] mikem edited comment on DERBY-3607 at 6/17/08 5:40 PM: ---------------------------------------------------------------- could you remove the db shutdown hook and see if you can reproduce the bug. Is it possible that the shutdown hook is running in a different class loader from the class loader that started the db/connects to the db? I didn't think DERBY-700 applied on windows, but doing the above experiment will give some important information. was (Author: mikem): could you remove the db shutdown hook and see if you can reproduce the bug. Is it possible that the shutdown hook is running in a different class loader from the class loader that started the db/connects to the 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: DB_10.4logs.zip, derby.log, derby.log, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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] 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=12605786#action_12605786 ] mikem edited comment on DERBY-3607 at 6/17/08 6:45 PM: ---------------------------------------------------------------- could you remove the db shutdown hook and see if you can reproduce the bug. Is it possible that the shutdown hook is running in a different class loader from the class loader that started the db/connects to the db? I didn't think DERBY-700 applied on windows, but doing the above experiment will give some important information. It may help to post the code for all of your shutdown hooks. From before it looks like there is 1 for shutting down the derby SYSTEM, and thus all the dbs. You describe another that shutdowns the clents - is there one or maybe one per db? Any others that are related to derby? was (Author: mikem): could you remove the db shutdown hook and see if you can reproduce the bug. Is it possible that the shutdown hook is running in a different class loader from the class loader that started the db/connects to the db? I didn't think DERBY-700 applied on windows, but doing the above experiment will give some important information. > 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, derby.log, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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 ] Shahbaz updated DERBY-3607: --------------------------- Attachment: DerbyIssues_DBSource.zip Please find the attached classes for all DB start ups and shut down. We have two DBs Arena and NetworkManager. ae.sphere.arena.networkManager.db.NetworkManagerDBStartup is the startup class of NM db ae.sphere.arena.arena.db.ArenaDBStartup is the startup class of Arena db ae.sphere.arena.database.management.shutdown.AddDBShutdownThreadHook is where we are adding jvm hooks for shutdown's. From hibernate level we are clearing sessions individualy but fron derby level its single which can be found in shutdownDB() menthod of ae.sphere.arena.database.common.management.DBManager class. > 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, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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: ---------------------------------- Without more info or a reproducible case I have run out of ideas on this one. I looked through the source you posted and nothing jumped out as wrong. Running shutdown as part of a jvmhook does put the code in probably an untested area of the JVM. As I read it all shutdown hook things runn concurrently so maybe there is a timing thing there. I started wondering if any of the cross class loader locking that we count on in XP stop working as various shutdown stuff happens. For instance at what point during jvm shutdown does the open file we have on the db lock file actually get closed? I could not tell from the code if there are actually multiple class loaders involved in your app accessing a single derby db. If I had a reproducible case I would run the application with the following properties: derby.stream.error.logSeverityLevel=0 derby.storage.keepTransactionLog=true derby.language.logStatementText=true derby.infolog.append=true This will require a lot of disk space. The keepTransactionLog property will keep all the transaction log files so after the fact one can see the exact history of the updating transactions during the test run. logStatementText helps with tracking the non-updating queries and will generate a huge derby.log. > 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, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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=12608790#action_12608790 ] Knut Anders Hatlen commented on DERBY-3607: ------------------------------------------- It could be worth a try to check if the fix for DERBY-3726 made any difference. The fix is available if you check out and build the latest development sources (trunk), the 10.4 branch or 10.3 branch. Alternatively, if you don't want to build it yourself, the jar files used in the nightly regression tests can be used to test it. See http://dbtg.thresher.com/derby/bits/. > 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, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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 ] Shahbaz updated DERBY-3607: --------------------------- Attachment: derby.log Hi, Sorry guys couldn't come on this issue, as I was busy. I have started logging of Derby, and also found the issue. I have attached the file for your reference. > 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, derby.log, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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=12613187#action_12613187 ] Shahbaz commented on DERBY-3607: -------------------------------- Just wondering, we have 2 databases arena and networkManager, but in logs we are getting only db/arena logs, which can be seen in previous attached derby log file, athough both dbs are initialized and working. > 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, derby.log, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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=12613196#action_12613196 ] Shahbaz commented on DERBY-3607: -------------------------------- As suggected by Knut, I checked with latest build, still the same problem in the same place. > 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, derby.log, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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=12639317#action_12639317 ] sunil kumar K C commented on DERBY-3607: ---------------------------------------- We are still facing the db corruption issue and it blocks most of our product installations. I have created an FTP site and uploaded the repro with instructions to do the test.kindly make use of it and give us some solution for this issue. I guess somehow the synchronization between the page file and memory container info goes wrong which results invalid page entries on the disk. As a result when we restart the application the corrupted page loads into the memory resulting in entire db crash.I can give you more information regarding our application set up if you need. FTP details address- ftp.sphere.ae username - anmderby password - 12345 Thanks and regards Sunil > 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, derby.log, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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=12639482#action_12639482 ] Kathey Marsden commented on DERBY-3607: --------------------------------------- I'm not seeing any files at that ftp address. > 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, derby.log, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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=12639517#action_12639517 ] sunil kumar K C commented on DERBY-3607: ---------------------------------------- Hi Kathey, The files are already there . i am able to see the files through the ftp from command prompt ftp> open ftp.sphere.ae Connected to sphere.ae. 220 Microsoft FTP Service User (sphere.ae:(none)): anmderby 331 Password required for anmderby. Password: 230 User anmderby logged in. ftp> dir 200 PORT command successful. 150 Opening ASCII mode data connection for /bin/ls. 10-13-08 09:27PM 30148639 ACM_1.1.0.exe 10-13-08 10:39PM 197208650 ANM_2.3.8.exe 10-13-08 09:27PM <DIR> db 10-13-08 09:05PM 1459 installation and testing procedure.txt 10-13-08 09:05PM 4318 wrapper.conf 226 Transfer complete. ftp: 283 bytes received in 0.00Seconds 70.75Kbytes/sec. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list. ACM_1.1.0.exe ANM_2.3.8.exe db installation and testing procedure.txt wrapper.conf 226 Transfer complete. ftp: 88 bytes received in 0.00Seconds 29.33Kbytes/sec. ftp> > 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, derby.log, derby.log, DerbyIssues_DBSource.zip, hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties, 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 |
