[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] Created: (DERBY-3607) Invalid checksum error in Derby 10.3.2.1
by JIRA jira@apache.org
::
Rate this Message:
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 Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3 Reporter: Shahbaz Priority: Blocker 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... 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: --------------------------- Description: 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 was: 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... 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 > 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 > Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3 > Reporter: Shahbaz > Priority: Blocker > > 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 ] Dyre Tjeldvoll updated DERBY-3607: ---------------------------------- Priority: Critical (was: Blocker) Downgrading this under the assumption that it is a duplicate of DERBY-3347 > 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 > Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3 > Reporter: Shahbaz > Priority: Critical > > 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=12592776#action_12592776 ] Shahbaz commented on DERBY-3607: -------------------------------- Its not the same issue as 3347, as for our use case it happens only when we try to restart our application. We are running two DBs 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 > Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3 > Reporter: Shahbaz > Priority: Critical > > 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=12592787#action_12592787 ] Kristian Waagan commented on DERBY-3607: ---------------------------------------- Can you explain what you mean with running two DBs in embedded mode? What I want to make sure of, is that you don't run two Derby instances (two JVMs) against a single database directory. Also, have you tried using the new 10.4.1.3 release? If you try, start with a fresh database. Upgrading Derby will not fix the database if it has already been corrupted. > 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 > Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3 > Reporter: Shahbaz > Priority: Critical > > 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=12592789#action_12592789 ] Shahbaz commented on DERBY-3607: -------------------------------- We tried both of the cases, but in actual implementation it is one process, we have tried latest release also but the same result. Its corrupting only some tables. Here are some more logs Caused by: java.sql.SQLException: Invalid checksum on Page Page(0,Container(0, 1568)), expected=2,264,079,051, on-disk version=6,651,942,472,428,708,205, 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... 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 0000 0000 0000 0000 0000 0000 0000 ................ 000000c0: 0000 0010 0000 0000 0000 0000 2a73 7973 .............sys 000000d0: 2d70 6163 6b61 6765 2d6d 6772 2a3a 2070 .package.mgr...p 000000e0: 726f 6365 7373 696e 6720 6e65 7720 6a61 rocessing.new.ja 000000f0: 722c 2027 433a 5c50 726f 6772 616d 2046 r...C..Program.F 00000100: 696c 6573 5c53 7068 6572 6520 4e65 7477 iles.Sphere.Netw 00000110: 6f72 6b73 5c41 7265 6e61 2050 6c61 7466 orks.Arena.Platf 00000120: 6f72 6d5c 706c 7567 696e 735c 6165 2e73 orm.plugins.ae.s 00000130: 7068 6572 652e 6172 656e 612e 6e65 7477 phere.arena.netw 00000140: 6f72 6b4d 616e 6167 6572 2e63 6f6d 6d6f orkManager.commo 00000150: 6e5f 322e 322e 315c 636f 6d6d 6f6e 2e6a n.2.2.1.common.j 00000160: 6172 270d 0a2a 7379 732d 7061 636b 6167 ar....sys.packag 00000170: 652d 6d67 722a 3a20 7072 6f63 6573 7369 e.mgr...processi 00000180: 6e67 206e 6577 206a 6172 2c20 2743 3a5c ng.new.jar...C.. 00000190: 5072 6f67 7261 6d20 4669 6c65 735c 5370 Program.Files.Sp 000001a0: 6865 7265 204e 6574 776f 726b 735c 4172 here.Networks.Ar 000001b0: 656e 6120 506c 6174 666f 726d 5c70 6c75 ena.Platform.plu 000001c0: 6769 6e73 5c61 652e 7370 6865 7265 2e61 gins.ae.sphere.a 000001d0: 7265 6e61 2e73 6572 7665 722e 6576 656e rena.server.even 000001e0: 744d 616e 6167 6572 5f32 2e32 2e31 5c65 tManager.2.2.1.e 000001f0: 7665 6e74 4d61 6e61 6765 722e 6a61 7227 ventManager.jar. 00000200: 0d0a 2a73 7973 2d70 6163 6b61 6765 2d6d ...sys.package.m 00000210: 6772 2a3a 2070 726f 6365 7373 696e 6720 gr...processing. 00000220: 6e65 7720 6a61 722c 2027 433a 5c50 726f new.jar...C..Pro 00000230: 6772 616d 2046 696c 6573 5c53 7068 6572 gram.Files.Spher 00000240: 6520 4e65 7477 6f72 6b73 5c41 7265 6e61 e.Networks.Arena 00000250: 2050 6c61 7466 6f72 6d5c 706c 7567 696e .Platform.plugin 00000260: 735c 6165 2e73 7068 6572 652e 6172 656e s.ae.sphere.aren 00000270: 612e 7365 7276 6572 2e65 7665 6e74 4d61 a.server.eventMa 00000280: 6e61 6765 725f 322e 322e 315c 6c69 625c nager.2.2.1.lib. 00000290: 6163 7469 7661 7469 6f6e 2e6a 6172 270d activation.jar.. 000002a0: 0a2a 7379 732d 7061 636b 6167 652d 6d67 ..sys.package.mg 000002b0: 722a 3a20 7072 6f63 6573 7369 6e67 206e r...processing.n 000002c0: 6577 206a 6172 2c20 2743 3a5c 5072 6f67 ew.jar...C..Prog 000002d0: 7261 6d20 4669 6c65 735c 5370 6865 7265 ram.Files.Sphere 000002e0: 204e 6574 776f 726b 735c 4172 656e 6120 .Networks.Arena. 000002f0: 506c 6174 666f 726d 5c70 6c75 6769 6e73 Platform.plugins 00000300: 5c61 652e 7370 6865 7265 2e61 7265 6e61 .ae.sphere.arena 00000310: 2e73 6572 7665 722e 6576 656e 744d 616e .server.eventMan 00000320: 6167 6572 5f32 2e32 2e31 5c6c 6962 5c6a ager.2.2.1.lib.j 00000330: 616b 6172 7461 2d72 6567 6578 702d 312e akarta.regexp.1. 00000340: 322e 6a61 7227 0d0a 2a73 7973 2d70 6163 2.jar....sys.pac 00000350: 6b61 6765 2d6d 6772 2a3a 2070 726f 6365 kage.mgr...proce 00000360: 7373 696e 6720 6e65 7720 6a61 722c 2027 ssing.new.jar... 00000370: 433a 5c50 726f 6772 616d 2046 696c 6573 C..Program.Files 00000380: 5c53 7068 6572 6520 4e65 7477 6f72 6b73 .Sphere.Networks 00000390: 5c41 7265 6e61 2050 6c61 7466 6f72 6d5c .Arena.Platform. 000003a0: 706c 7567 696e 735c 6165 2e73 7068 6572 plugins.ae.spher 000003b0: 652e 6172 656e 612e 7365 7276 6572 2e65 e.arena.server.e 000003c0: 7665 6e74 4d61 6e61 6765 725f 322e 322e ventManager.2.2. 000003d0: 315c 6c69 625c 4a43 7570 2e6a 6172 270d 1.lib.JCup.jar.. 000003e0: 0a2a 7379 732d 7061 636b 6167 652d 6d67 ..sys.package.mg 000003f0: 722a 3a20 7072 6f63 6573 7369 6e67 206e r...processing.n 00000400: 6577 206a 6172 2c20 2743 3a5c 5072 6f67 ew.jar...C..Prog 00000410: 7261 6d20 4669 6c65 735c 5370 6865 7265 ram.Files.Sphere 00000420: 204e 6574 776f 726b 735c 4172 656e 6120 .Networks.Arena. 00000430: 506c 6174 666f 726d 5c70 6c75 6769 6e73 Platform.plugins 00000440: 5c61 652e 7370 6865 7265 2e61 7265 6e61 .ae.sphere.arena 00000450: 2e73 6572 7665 722e 6576 656e 744d 616e .server.eventMan 00000460: 6167 6572 5f32 2e32 2e31 5c6c 6962 5c6a ager.2.2.1.lib.j 00000470: 6772 6f75 7073 2d61 6c6c 2e6a 6172 270d groups.all.jar.. 00000480: 0a2a 7379 732d 7061 636b 6167 652d 6d67 ..sys.package.mg 00000490: 722a 3a20 7072 6f63 6573 7369 6e67 206e r...processing.n 000004a0: 6577 206a 6172 2c20 2743 3a5c 5072 6f67 ew.jar...C..Prog 000004b0: 7261 6d20 4669 6c65 735c 5370 6865 7265 ram.Files.Sphere 000004c0: 204e 6574 776f 726b 735c 4172 656e 6120 .Networks.Arena. 000004d0: 506c 6174 666f 726d 5c70 6c75 6769 6e73 Platform.plugins 000004e0: 5c61 652e 7370 6865 7265 2e61 7265 6e61 .ae.sphere.arena 000004f0: 2e73 6572 7665 722e 6576 656e 744d 616e .server.eventMan 00000500: 6167 6572 5f32 2e32 2e31 5c6c 6962 5c6a ager.2.2.1.lib.j 00000510: 6d73 2e6a 6172 270d 0a2a 7379 732d 7061 ms.jar....sys.pa 00000520: 636b 6167 652d 6d67 722a 3a20 7072 6f63 ckage.mgr...proc 00000530: 6573 7369 6e67 206e 6577 206a 6172 2c20 essing.new.jar.. 00000540: 2743 3a5c 5072 6f67 7261 6d20 4669 6c65 .C..Program.File 00000550: 735c 5370 6865 7265 204e 6574 776f 726b s.Sphere.Network 00000560: 735c 4172 656e 6120 506c 6174 666f 726d s.Arena.Platform 00000570: 5c70 6c75 6769 6e73 5c61 652e 7370 6865 .plugins.ae.sphe 00000580: 7265 2e61 7265 6e61 2e73 6572 7665 722e re.arena.server. 00000590: 6576 656e 744d 616e 6167 6572 5f32 2e32 eventManager.2.2 000005a0: 2e31 5c6c 6962 5c6a 6d78 7269 2e6a 6172 .1.lib.jmxri.jar 000005b0: 270d 0a2a 7379 732d 7061 636b 6167 652d ....sys.package. 000005c0: 6d67 722a 3a20 7072 6f63 6573 7369 6e67 mgr...processing 000005d0: 206e 6577 206a 6172 2c20 2743 3a5c 5072 .new.jar...C..Pr 000005e0: 6f67 7261 6d20 4669 6c65 735c 5370 6865 ogram.Files.Sphe 000005f0: 7265 204e 6574 776f 726b 735c 4172 656e re.Networks.Aren 00000600: 6120 506c 6174 666f 726d 5c70 6c75 6769 a.Platform.plugi 00000610: 6e73 5c61 652e 7370 6865 7265 2e61 7265 ns.ae.sphere.are 00000620: 6e61 2e73 6572 7665 722e 6576 656e 744d na.server.eventM 00000630: 616e 6167 6572 5f32 2e32 2e31 5c6c 6962 anager.2.2.1.lib 00000640: 5c6a 6d78 746f 6f6c 732e 6a61 7227 0d0a .jmxtools.jar... 00000650: 2a73 7973 2d70 6163 6b61 6765 2d6d 6772 .sys.package.mgr 00000660: 2a3a 2070 726f 6365 7373 696e 6720 6e65 ...processing.ne 00000670: 7720 6a61 722c 2027 433a 5c50 726f 6772 w.jar...C..Progr 00000680: 616d 2046 696c 6573 5c53 7068 6572 6520 am.Files.Sphere. 00000690: 4e65 7477 6f72 6b73 5c41 7265 6e61 2050 Networks.Arena.P 000006a0: 6c61 7466 6f72 6d5c 706c 7567 696e 735c latform.plugins. 000006b0: 6165 2e73 7068 6572 652e 6172 656e 612e ae.sphere.arena. 000006c0: 7365 7276 6572 2e65 7665 6e74 4d61 6e61 server.eventMana 000006d0: 6765 725f 322e 322e 315c 6c69 625c 6a6e ger.2.2.1.lib.jn 000006e0: 6469 2e6a 6172 270d 0a2a 7379 732d 7061 di.jar....sys.pa 000006f0: 636b 6167 652d 6d67 722a 3a20 7072 6f63 ckage.mgr...proc 00000700: 6573 7369 6e67 206e 6577 206a 6172 2c20 essing.new.jar.. 00000710: 2743 3a5c 5072 6f67 7261 6d20 4669 6c65 .C..Program.File 00000720: 735c 5370 6865 7265 204e 6574 776f 726b s.Sphere.Network 00000730: 735c 4172 656e 6120 506c 6174 666f 726d s.Arena.Platform 00000740: 5c70 6c75 6769 6e73 5c61 652e 7370 6865 .plugins.ae.sphe 00000750: 7265 2e61 7265 6e61 2e73 6572 7665 722e re.arena.server. 00000760: 6576 656e 744d 616e 6167 6572 5f32 2e32 eventManager.2.2 00000770: 2e31 5c6c 6962 5c6a 6f72 616d 2d63 6c69 .1.lib.joram.cli 00000780: 656e 742e 6a61 7227 0d0a 2a73 7973 2d70 ent.jar....sys.p 00000790: 6163 6b61 6765 2d6d 6772 2a3a 2070 726f ackage.mgr...pro 000007a0: 6365 7373 696e 6720 6e65 7720 6a61 722c cessing.new.jar. 000007b0: 2027 433a 5c50 726f 6772 616d 2046 696c ..C..Program.Fil 000007c0: 6573 5c53 7068 6572 6520 4e65 7477 6f72 es.Sphere.Networ 000007d0: 6b73 5c41 7265 6e61 2050 6c61 7466 6f72 ks.Arena.Platfor 000007e0: 6d5c 706c 7567 696e 735c 6165 2e73 7068 m.plugins.ae.sph 000007f0: 6572 652e 6172 656e 612e 7365 7276 6572 ere.arena.server 00000800: 2e65 7665 6e74 4d61 6e61 6765 725f 322e .eventManager.2. 00000810: 322e 315c 6c69 625c 6a6f 7261 6d2d 6d6f 2.1.lib.joram.mo 00000820: 6d2e 6a61 7227 0d0a 2a73 7973 2d70 6163 m.jar....sys.pac 00000830: 6b61 6765 2d6d 6772 2a3a 2070 726f 6365 kage.mgr...proce 00000840: 7373 696e 6720 6e65 7720 6a61 722c 2027 ssing.new.jar... 00000850: 433a 5c50 726f 6772 616d 2046 696c 6573 C..Program.Files 00000860: 5c53 7068 6572 6520 4e65 7477 6f72 6b73 .Sphere.Networks 00000870: 5c41 7265 6e61 2050 6c61 7466 6f72 6d5c .Arena.Platform. 00000880: 706c 7567 696e 735c 6165 2e73 7068 6572 plugins.ae.spher 00000890: 652e 6172 656e 612e 7365 7276 6572 2e65 e.arena.server.e 000008a0: 7665 6e74 4d61 6e61 6765 725f 322e 322e ventManager.2.2. 000008b0: 315c 6c69 625c 6a6f 7261 6d2d 7368 6172 1.lib.joram.shar 000008c0: 6564 2e6a 6172 270d 0a2a 7379 732d 7061 ed.jar....sys.pa 000008d0: 636b 6167 652d 6d67 722a 3a20 7072 6f63 ckage.mgr...proc 000008e0: 6573 7369 6e67 206e 6577 206a 6172 2c20 essing.new.jar.. 000008f0: 2743 3a5c 5072 6f67 7261 6d20 4669 6c65 .C..Program.File 00000900: 735c 5370 6865 7265 204e 6574 776f 726b s.Sphere.Network 00000910: 735c 4172 656e 6120 506c 6174 666f 726d s.Arena.Platform 00000920: 5c70 6c75 6769 6e73 5c61 652e 7370 6865 .plugins.ae.sphe 00000930: 7265 2e61 7265 6e61 2e73 6572 7665 722e re.arena.server. 00000940: 6576 656e 744d 616e 6167 6572 5f32 2e32 eventManager.2.2 00000950: 2e31 5c6c 6962 5c6a 7461 2e6a 6172 270d .1.lib.jta.jar.. 00000960: 0a2a 7379 732d 7061 636b 6167 652d 6d67 ..sys.package.mg 00000970: 722a 3a20 7072 6f63 6573 7369 6e67 206e r...processing.n 00000980: 6577 206a 6172 2c20 2743 3a5c 5072 6f67 ew.jar...C..Prog 00000990: 7261 6d20 4669 6c65 735c 5370 6865 7265 ram.Files.Sphere 000009a0: 204e 6574 776f 726b 735c 4172 656e 6120 .Networks.Arena. 000009b0: 506c 6174 666f 726d 5c70 6c75 6769 6e73 Platform.plugins 000009c0: 5c61 652e 7370 6865 7265 2e61 7265 6e61 .ae.sphere.arena 000009d0: 2e73 6572 7665 722e 6576 656e 744d 616e .server.eventMan 000009e0: 6167 6572 5f32 2e32 2e31 5c6c 6962 5c6b ager.2.2.1.lib.k 000009f0: 786d 6c2e 6a61 7227 0d0a 2a73 7973 2d70 xml.jar....sys.p 00000a00: 6163 6b61 6765 2d6d 6772 2a3a 2070 726f ackage.mgr...pro 00000a10: 6365 7373 696e 6720 6e65 7720 6a61 722c cessing.new.jar. 00000a20: 2027 433a 5c50 726f 6772 616d 2046 696c ..C..Program.Fil 00000a30: 6573 5c53 7068 6572 6520 4e65 7477 6f72 es.Sphere.Networ 00000a40: 6b73 5c41 7265 6e61 2050 6c61 7466 6f72 ks.Arena.Platfor 00000a50: 6d5c 706c 7567 696e 735c 6165 2e73 7068 m.plugins.ae.sph 00000a60: 6572 652e 6172 656e 612e 7365 7276 6572 ere.arena.server 00000a70: 2e65 7665 6e74 4d61 6e61 6765 725f 322e .eventManager.2. 00000a80: 322e 315c 6c69 625c 6d69 6470 6170 692e 2.1.lib.midpapi. 00000a90: 6a61 7227 0d0a 2a73 7973 2d70 6163 6b61 jar....sys.packa 00000aa0: 6765 2d6d 6772 2a3a 2070 726f 6365 7373 ge.mgr...process 00000ab0: 696e 6720 6e65 7720 6a61 722c 2027 433a ing.new.jar...C. 00000ac0: 5c50 726f 6772 616d 2046 696c 6573 5c53 .Program.Files.S 00000ad0: 7068 6572 6520 4e65 7477 6f72 6b73 5c41 phere.Networks.A 00000ae0: 7265 6e61 2050 6c61 7466 6f72 6d5c 706c rena.Platform.pl 00000af0: 7567 696e 735c 6165 2e73 7068 6572 652e ugins.ae.sphere. 00000b00: 6172 656e 612e 7365 7276 6572 2e65 7665 arena.server.eve 00000b10: 6e74 4d61 6e61 6765 725f 322e 322e 315c ntManager.2.2.1. 00000b20: 6c69 625c 6f77 5f6d 6f6e 6f6c 6f67 2e6a lib.ow.monolog.j 00000b30: 6172 270d 0a2a 7379 732d 7061 636b 6167 ar....sys.packag 00000b40: 652d 6d67 722a 3a20 7072 6f63 6573 7369 e.mgr...processi 00000b50: 6e67 206e 6577 206a 6172 2c20 2743 3a5c ng.new.jar...C.. 00000b60: 5072 6f67 7261 6d20 4669 6c65 735c 5370 Program.Files.Sp 00000b70: 6865 7265 204e 6574 776f 726b 735c 4172 here.Networks.Ar 00000b80: 656e 6120 506c 6174 666f 726d 5c70 6c75 ena.Platform.plu 00000b90: 6769 6e73 5c61 652e 7370 6865 7265 2e61 gins.ae.sphere.a 00000ba0: 7265 6e61 2e73 6572 7665 722e 6576 656e rena.server.even 00000bb0: 744d 616e 6167 6572 5f32 2e32 2e31 5c6c tManager.2.2.1.l 00000bc0: 6962 5c73 6f61 702e 6a61 7227 0d0a 2a73 ib.soap.jar....s 00000bd0: 7973 2d70 6163 6b61 6765 2d6d 6772 2a3a ys.package.mgr.. 00000be0: 2070 726f 6365 7373 696e 6720 6e65 7720 .processing.new. 00000bf0: 6a61 722c 2027 433a 5c50 726f 6772 616d jar...C..Program 00000c00: 2046 696c 6573 5c53 7068 6572 6520 4e65 .Files.Sphere.Ne 00000c10: 7477 6f72 6b73 5c41 7265 6e61 2050 6c61 tworks.Arena.Pla 00000c20: 7466 6f72 6d5c 706c 7567 696e 735c 6165 tform.plugins.ae 00000c30: 2e73 7068 6572 652e 6172 656e 612e 6c6f .sphere.arena.lo 00000c40: 675f 322e 322e 315c 736c 6f67 2e6a 6172 g.2.2.1.slog.jar 00000c50: 270d 0a2a 7379 732d 7061 636b 6167 652d ....sys.package. 00000c60: 6d67 722a 3a20 7072 6f63 6573 7369 6e67 mgr...processing 00000c70: 206e 6577 206a 6172 2c20 2743 3a5c 5072 .new.jar...C..Pr 00000c80: 6f67 7261 6d20 4669 6c65 735c 5370 6865 ogram.Files.Sphe 00000c90: 7265 204e 6574 776f 726b 735c 4172 656e re.Networks.Aren 00000ca0: 6120 506c 6174 666f 726d 5c70 6c75 6769 a.Platform.plugi 00000cb0: 6e73 5c61 652e 7370 6865 7265 2e61 7265 ns.ae.sphere.are 00000cc0: 6e61 2e6c 6f67 5f32 2e32 2e31 5c6c 6962 na.log.2.2.1.lib 00000cd0: 5c63 6f6d 6d6f 6e73 2d6c 6f67 6769 6e67 .commons.logging 00000ce0: 2d31 2e30 2e34 2e6a 6172 270d 0a2a 7379 .1.0.4.jar....sy 00000cf0: 732d 7061 636b 6167 652d 6d67 722a 3a20 s.package.mgr... 00000d00: 7072 6f63 6573 7369 6e67 206e 6577 206a processing.new.j 00000d10: 6172 2c20 2743 3a5c 5072 6f67 7261 6d20 ar...C..Program. 00000d20: 4669 6c65 735c 5370 6865 7265 204e 6574 Files.Sphere.Net 00000d30: 776f 726b 735c 4172 656e 6120 506c 6174 works.Arena.Plat 00000d40: 666f 726d 5c70 6c75 6769 6e73 5c61 652e form.plugins.ae. 00000d50: 7370 6865 7265 2e61 7265 6e61 2e6c 6f67 sphere.arena.log 00000d60: 5f32 2e32 2e31 5c6c 6962 5c6c 6f67 346a .2.2.1.lib.log4j 00000d70: 2d31 2e32 2e31 322e 6a61 7227 0d0a 2a73 .1.2.12.jar....s 00000d80: 7973 2d70 6163 6b61 6765 2d6d 6772 2a3a ys.package.mgr.. 00000d90: 2070 726f 6365 7373 696e 6720 6e65 7720 .processing.new. 00000da0: 6a61 722c 2027 433a 5c50 726f 6772 616d jar...C..Program 00000db0: 2046 696c 6573 5c53 7068 6572 6520 4e65 .Files.Sphere.Ne 00000dc0: 7477 6f72 6b73 5c41 7265 6e61 2050 6c61 tworks.Arena.Pla 00000dd0: 7466 6f72 6d5c 706c 7567 696e 735c 6165 tform.plugins.ae 00000de0: 2e73 7068 6572 652e 6172 656e 612e 6e65 .sphere.arena.ne 00000df0: 7477 6f72 6b4d 616e 6167 6572 2e64 6973 tworkManager.dis 00000e00: 636f 7665 7279 5f32 2e33 2e30 5c64 6973 covery.2.3.0.dis 00000e10: 636f 7665 7279 2e6a 6172 270d 0a2a 7379 covery.jar....sy 00000e20: 732d 7061 636b 6167 652d 6d67 722a 3a20 s.package.mgr... 00000e30: 7072 6f63 6573 7369 6e67 206e 6577 206a processing.new.j 00000e40: 6172 2c20 2743 3a5c 5072 6f67 7261 6d20 ar...C..Program. 00000e50: 4669 6c65 735c 5370 6865 7265 204e 6574 Files.Sphere.Net 00000e60: 776f 726b 735c 4172 656e 6120 506c 6174 works.Arena.Plat 00000e70: 666f 726d 5c70 6c75 6769 6e73 5c61 652e form.plugins.ae. 00000e80: 7370 6865 7265 2e61 7265 6e61 2e73 6572 sphere.arena.ser 00000e90: 7665 725f 322e 322e 315c 6172 656e 6153 ver.2.2.1.arenaS 00000ea0: 6572 7665 722e 6a61 7227 0d0a 2a73 7973 erver.jar....sys 00000eb0: 2d70 6163 6b61 6765 2d6d 6772 2a3a 2070 .package.mgr...p 00000ec0: 726f 6365 7373 696e 6720 6e65 7720 6a61 rocessing.new.ja 00000ed0: 722c 2027 433a 5c50 726f 6772 616d 2046 r...C..Program.F 00000ee0: 696c 6573 5c53 7068 6572 6520 4e65 7477 iles.Sphere.Netw 00000ef0: 6f72 6b73 5c41 7265 6e61 2050 6c61 7466 orks.Arena.Platf 00000f00: 6f72 6d5c 706c 7567 696e 735c 6165 2e73 orm.plugins.ae.s 00000f10: 7068 6572 652e 6172 656e 612e 636f 6d6d phere.arena.comm 00000f20: 6f6e 5f32 2e32 2e31 5c63 6f6d 6d6f 6e2e on.2.2.1.common. 00000f30: 6a61 7227 0d0a 2a73 7973 2d70 6163 6b61 jar....sys.packa 00000f40: 6765 2d6d 6772 2a3a 2070 726f 6365 7373 ge.mgr...process 00000f50: 696e 6720 6e65 7720 6a61 722c 2027 433a ing.new.jar...C. 00000f60: 5c50 726f 6772 616d 2046 696c 6573 5c53 .Program.Files.S 00000f70: 7068 6572 6520 4e65 7477 6f72 6b73 5c41 phere.Networks.A 00000f80: 7265 6e61 2050 6c61 7466 6f72 6d5c 706c rena.Platform.pl 00000f90: 7567 696e 735c 6165 2e73 7068 6572 652e ugins.ae.sphere. 00000fa0: 6172 656e 612e 636f 6d6d 6f6e 5f32 2e32 arena.common.2.2 00000fb0: 2e31 5c6c 6962 5c63 6f6d 6d6f 6e73 2d6c .1.lib.commons.l 00000fc0: 616e 672d 322e 332e 6a61 7227 0d0a 2a73 ang.2.3.jar....s 00000fd0: 7973 2d70 6163 6b61 6765 2d6d 6772 2a3a ys.package.mgr.. 00000fe0: 2070 726f 6365 7373 696e 6720 6e65 7720 .processing.new. 00000ff0: 6a61 722c 2027 433a 5c50 726f 6772 616d jar...C..Program 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.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 sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask.run(GooGooStatementCache.java:525) at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) > 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 > Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3 > Reporter: Shahbaz > Priority: Critical > > 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: --------------------------- Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3,c3p0 (was: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching disabled, Hibernate 3.1.1.RC3) Affects Version/s: 10.4.1.3 > 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 > > 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=12592800#action_12592800 ] Kristian Waagan commented on DERBY-3607: ---------------------------------------- Okay. I see that you are using c3p0, I assume it is for connection pooling? Can you try to disable it? We know there are some problems using it with Derby, because it may interrupt threads. I'm not sure if that is still the case for the newest version of c3p0. Another option is to use the client driver instead of the embedded driver, and see if you still get the corruption. > 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 > > 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=12592971#action_12592971 ] Shahbaz commented on DERBY-3607: -------------------------------- I disbled c3p0, it has reduced the curruption, but it again happened when I tried to restart my service 4-5 times, Logs: ------------ BEGIN SHUTDOWN ERROR STACK ------------- ERROR XSDG2: Invalid checksum on Page Page(0,Container(0, 289)), expected=4,121,030,011, on-disk version=3,162,187,389, page dump follows: Hex dump: 00000000: 0076 0000 0001 0000 0000 0000 0004 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... 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 ................ at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.store.raw.data.StoredPage.validateChecksum(Unknown Source) at org.apache.derby.impl.store.raw.data.StoredPage.initFromData(Unknown Source) at org.apache.derby.impl.store.raw.data.AllocPage.initFromData(Unknown Source) at org.apache.derby.impl.store.raw.data.CachedPage.setIdentity(Unknown Source) at org.apache.derby.impl.store.raw.data.CachedPage.setIdentity(Unknown Source) at org.apache.derby.impl.services.cache.CachedItem.takeOnIdentity(Unknown Source) at org.apache.derby.impl.services.cache.Clock.addEntry(Unknown Source) at org.apache.derby.impl.services.cache.Clock.find(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.getAllocPage(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseContainer.getAllocPage(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseContainerHandle.getAllocPage(Unknown Source) at org.apache.derby.impl.store.raw.data.AllocationCache.validate(Unknown Source) at org.apache.derby.impl.store.raw.data.AllocationCache.getLastPageNumber(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.pageValid(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.getUserPage(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.getPage(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseContainerHandle.getPage(Unknown Source) at org.apache.derby.impl.store.access.btree.ControlRow.get(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.openScan(Unknown Source) at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getConstraintDescriptorViaIndex(Unknown Source) at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getConstraintDescriptorsScan(Unknown Source) at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getConstraintDescriptors(Unknown Source) at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getConstraintDescriptor(Unknown Source) at org.apache.derby.impl.sql.compile.AccessPathImpl.initializeAccessPathName(Unknown Source) at org.apache.derby.impl.sql.compile.FromTable.rememberAsBest(Unknown Source) at org.apache.derby.impl.sql.compile.ProjectRestrictNode.rememberAsBest(Unknown Source) at org.apache.derby.impl.sql.compile.OptimizerImpl.rememberBestCost(Unknown Source) at org.apache.derby.impl.sql.compile.OptimizerImpl.getNextDecoratedPermutation(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.hql.QueryLoader.list(QueryLoader.java:369) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:298) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:137) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1014) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:750) at ae.sphere.arena.networkManager.db.dao._RootDAO.getCount(_RootDAO.java:130) at ae.sphere.arena.configurationManager.db.ConfManagerDBStartup$1.run(ConfManagerDBStartup.java:62) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) > 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 > > 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=12592984#action_12592984 ] Shahbaz commented on DERBY-3607: -------------------------------- Its ok if I am using 2 DBs but when I tried for 3rd DB in embedded mode with out c3p0, the same problem appeared again. I am attaching some files for 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 > > 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: hibernate.cfg.xml hibernate.cfg.xml derby.log Logs and hibernate cfg files > 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, 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: hibernate.cfg.xml hibernate cfg files > 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, 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=12593001#action_12593001 ] Kristian Waagan commented on DERBY-3607: ---------------------------------------- I see in your Hibernate configuration file that there is a line commented out for using the client driver. Have you tried running with the the client driver? It would be interesting to see if that fails as well, because that would indicate there is another bug than the thread interruption issue in play. > 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, 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: ---------------------------------- I can't tell from the comments. Have you reproduced this problem starting fresh from a new uncorrupted database against the latest 10.4 release or a hand built 10.3 release with the recent I/O bug fixed? Once a checksum error happens it is unlikely any future release will fix it. So if your application has an existing db embedded in it with the error no future software is likely to fix it. > 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, 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=12593979#action_12593979 ] Shahbaz commented on DERBY-3607: -------------------------------- When I put all our DBs on client driver (network mode), upto now its working fine, but testing is going on. but we will prefer to have in embedded mode. Why its failing 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: 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=12593988#action_12593988 ] Kristian Waagan commented on DERBY-3607: ---------------------------------------- That's great Shahbaz. I would appreciate if you kept running with the client driver for a while longer to be more certain that the corruption doesn't happen there. I can't tell you for sure, but the theory is that something is interrupting the Derby threads when they are writing data to disk. In previous cases we have seen lately, this something has been c3p0. Note that this is just a theory, and we need to look further into it. Also, I do not know if the latest version of c3p0 has this "problem" or even if it is c3p0 causing the trouble. I don't have the overview to tell what needs to be done, but in my opinion it seems Derby is not able to protect itself well enough from these kinds of actions (thread interruption). If you have all your source code easily available, you could check if there is any code calling Thread.interrupt(). Another step, since you seem to be able to reproduce this pretty easy, is to instrument Derby with some debugging code checking if the threads are indeed interrupted. Out of curiosity, is the software stack you are using freely available, so Derby developers could run it and provoke the error if they wish to do so? > 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, 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=12594070#action_12594070 ] Shahbaz commented on DERBY-3607: -------------------------------- Upto now its working fine with client drvier and still in testing. I also checked our code and we dont have Thread.interrupt() case, It looks to me straight forward. I am sorry s/w is not freely available but let me try to give you enough, so that derby developers can reproduce 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: 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=12599687#action_12599687 ] Shahbaz commented on DERBY-3607: -------------------------------- Its not happening with client driver after several testing but we can reproduce the same using embedded mode in just one or two attempts. > 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, 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=12599703#action_12599703 ] Kristian Waagan commented on DERBY-3607: ---------------------------------------- It's good to know that the client driver isn't experiencing the bug. Thanks for testing it! Now, to get this fixed in the embedded driver, it would be really helpful to get a repro we can run. Are you still planning on providing one? If not, it's very hard to fix the bug, as we don't know the cause. One could guess and try to put some tracing code into a custom build, but that means someone has to do this and then you have to run it in your system to test it out. I'm not sure how excited developers will be about such a bug fixing cycle :) Further, I guess we don't know when the corruption is happening, only that you see it when you restart Derby. > 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, 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: ---------------------------------- can you reproduce this in embedded, starting with a new database using the 10.3.3.0 release? This release has a fix for a serious problem with I/O access to page 0. It is important to differentiate between testing against the new release with a new database and testing against the new release with an existine database. Unfortunately once the problem happens no future software version can fix the problem. You can see more info about this problem and the announcement of the recent release here: http://mail-archives.apache.org/mod_mbox/db-derby-user/200805.mbox/%3c54ac72d70805211242y29d4a0bcyf6ae518a7a8f1767@...%3e > 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, 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. |
| < Prev | 1 - 2 - 3 - 4 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
