Re: [h2] corrupt database 1.3.168
I'm sure the corruption was not there using 1.3.161 because its just an empty scheme I created once back then (i can send it if it helps). Whatever happens in that file later on, happens by a more recent h2.jar (1.3.168 in this report). I completely understand there's nothing you can do without a .db file or reproducible test. Op dinsdag 1 oktober 2013 19:36:04 UTC+2 schreef Thomas Mueller: Hi, Well, the problem is, if the database was created with an old version, then the corruption might have been there already when you switched to a new version. Corruption problems are very hard to analyze, because there is no log file that tells us which change in the database file was created by which version of H2... Of course, if the problem is reproducible, yes, that's another case. Reproducible problems are usually quite easy to analyze and fix. Regards, Thomas On Tue, Oct 1, 2013 at 4:12 PM, Dieter Cailliau dieter@gmail.comjavascript: wrote: I assume that that fact (that the h2 version with which i created the schema = 1.3.161) is not relevant for the problem experienced in 1.3.168 which is still a problem in 1.3.168? It is true that i have created a schema once using an older h2, and kept that db file as a file to start of in my app, even though i've been upgrading h2.jar along in my app. If this is a problem (using this db file against an uptodate h2.jar), please tell me. Op woensdag 21 augustus 2013 07:43:45 UTC+2 schreef Thomas Mueller: Hi, The empty database was created with version 1.3.161, as the CREATE_BUILD is 161. Since then, a few bugs have been fixed that could cause corruption; see the change log for details. I suggest to try again with a more recent version of H2. If it is still a problem, it would be great if you could provide a simple, reproducible test case. Regards, Thomas On Tuesday, August 13, 2013, Dieter Cailliau wrote: jdbc:h2:/tmp/x;DB_CLOSE_DELAY=**-1;LOCK_TIMEOUT=5000 It's a small db (3M on a windows7) with small tables (about 100 rows). I'm using multiple threads. I attached the empty schema. If it helps i can send you a (non-corrupt) populated one. I'm still trying to reproduce the corruption. While reading the list, i learned that h2 performs a corruption correction at open-time: i think that does not help, because the opening succeeds, but later that query fails. Thanks! Op dinsdag 13 augustus 2013 10:18:19 UTC+2 schreef Noel Grandin: On 2013-08-13 10:05, Dieter Cailliau wrote: Here's another example of ArrayIndexOutOfBoundsException at org.h2.index.PageDataLeaf.**getR**owAt: this happened on 1.3.168. The most recent fix i found in changelog about this kind of error was 1.3.166, so probably there's still something wrong since then, or have there been fixes related to this, since 1.3.168? What does your database URL look like? -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscribe@**googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/**group/h2-databasehttp://groups.google.com/group/h2-database . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database...@googlegroups.com javascript:. To post to this group, send email to h2-da...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
Re: [h2] corrupt database 1.3.168
I assume that that fact (that the h2 version with which i created the schema = 1.3.161) is not relevant for the problem experienced in 1.3.168 which is still a problem in 1.3.168? It is true that i have created a schema once using an older h2, and kept that db file as a file to start of in my app, even though i've been upgrading h2.jar along in my app. If this is a problem (using this db file against an uptodate h2.jar), please tell me. Op woensdag 21 augustus 2013 07:43:45 UTC+2 schreef Thomas Mueller: Hi, The empty database was created with version 1.3.161, as the CREATE_BUILD is 161. Since then, a few bugs have been fixed that could cause corruption; see the change log for details. I suggest to try again with a more recent version of H2. If it is still a problem, it would be great if you could provide a simple, reproducible test case. Regards, Thomas On Tuesday, August 13, 2013, Dieter Cailliau wrote: jdbc:h2:/tmp/x;DB_CLOSE_DELAY=-1;LOCK_TIMEOUT=5000 It's a small db (3M on a windows7) with small tables (about 100 rows). I'm using multiple threads. I attached the empty schema. If it helps i can send you a (non-corrupt) populated one. I'm still trying to reproduce the corruption. While reading the list, i learned that h2 performs a corruption correction at open-time: i think that does not help, because the opening succeeds, but later that query fails. Thanks! Op dinsdag 13 augustus 2013 10:18:19 UTC+2 schreef Noel Grandin: On 2013-08-13 10:05, Dieter Cailliau wrote: Here's another example of ArrayIndexOutOfBoundsException at org.h2.index.PageDataLeaf.**getRowAt: this happened on 1.3.168. The most recent fix i found in changelog about this kind of error was 1.3.166, so probably there's still something wrong since then, or have there been fixes related to this, since 1.3.168? What does your database URL look like? -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
Re: [h2] corrupt database 1.3.168
Hi, Well, the problem is, if the database was created with an old version, then the corruption might have been there already when you switched to a new version. Corruption problems are very hard to analyze, because there is no log file that tells us which change in the database file was created by which version of H2... Of course, if the problem is reproducible, yes, that's another case. Reproducible problems are usually quite easy to analyze and fix. Regards, Thomas On Tue, Oct 1, 2013 at 4:12 PM, Dieter Cailliau dieter.caill...@gmail.comwrote: I assume that that fact (that the h2 version with which i created the schema = 1.3.161) is not relevant for the problem experienced in 1.3.168 which is still a problem in 1.3.168? It is true that i have created a schema once using an older h2, and kept that db file as a file to start of in my app, even though i've been upgrading h2.jar along in my app. If this is a problem (using this db file against an uptodate h2.jar), please tell me. Op woensdag 21 augustus 2013 07:43:45 UTC+2 schreef Thomas Mueller: Hi, The empty database was created with version 1.3.161, as the CREATE_BUILD is 161. Since then, a few bugs have been fixed that could cause corruption; see the change log for details. I suggest to try again with a more recent version of H2. If it is still a problem, it would be great if you could provide a simple, reproducible test case. Regards, Thomas On Tuesday, August 13, 2013, Dieter Cailliau wrote: jdbc:h2:/tmp/x;DB_CLOSE_DELAY=**-1;LOCK_TIMEOUT=5000 It's a small db (3M on a windows7) with small tables (about 100 rows). I'm using multiple threads. I attached the empty schema. If it helps i can send you a (non-corrupt) populated one. I'm still trying to reproduce the corruption. While reading the list, i learned that h2 performs a corruption correction at open-time: i think that does not help, because the opening succeeds, but later that query fails. Thanks! Op dinsdag 13 augustus 2013 10:18:19 UTC+2 schreef Noel Grandin: On 2013-08-13 10:05, Dieter Cailliau wrote: Here's another example of ArrayIndexOutOfBoundsException at org.h2.index.PageDataLeaf.**getR**owAt: this happened on 1.3.168. The most recent fix i found in changelog about this kind of error was 1.3.166, so probably there's still something wrong since then, or have there been fixes related to this, since 1.3.168? What does your database URL look like? -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscribe@**googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/**group/h2-databasehttp://groups.google.com/group/h2-database . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
[h2] corrupt database 1.3.168
Here's another example of ArrayIndexOutOfBoundsException at
org.h2.index.PageDataLeaf.getRowAt: this happened on 1.3.168. The most
recent fix i found in changelog about this kind of error was 1.3.166, so
probably there's still something wrong since then, or have there been fixes
related to this, since 1.3.168?
Unfortunately i don't have the corrupted db file.
Caused by: org.h2.jdbc.JdbcSQLException: General error:
java.lang.ArrayIndexOutOfBoundsException: 0; SQL statement:
select device0_.string as string5_, device0_.lastSeen as lastSeen5_,
device0_.sources as sources5_, device0_.id as id5_, device0_.name as
name5_, device0_.options as options5_, device0_.assets2 as assets8_5_,
device0_.parent_string as parent16_5_, device0_.boardNumber as
boardNum9_5_, device0_.outputBoardVersion as outputB11_5_,
device0_.rgbFromScaler as rgbFrom12_5_, device0_.timing as timing5_,
device0_.genlock as genlock5_, device0_.DTYPE as DTYPE5_ from Element
device0_ inner join Interface interfaces1_ on
device0_.string=interfaces1_.device_string where device0_.DTYPE in
('Device', 'a', 'b', 'c', 'd', 'e', 'f', 'g', 'h', 'i', 'j', 'k', 'l', 'm',
'n', 'o', 'p', 'q', 'r', 's', 't', 'u', 'v', 'w', 'w', 'y', 'z', 'aa',
'ab', 'ac', 'ad', 'ae', 'af', 'ag', 'ah', 'ai', 'aj', 'ak', 'al', 'am',
'an') and interfaces1_.DTYPE='RJ45Connector' order by device0_.string
[5-168]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:329)
[h2-1.3.168.jar:1.3.168]
at org.h2.message.DbException.get(DbException.java:158)
[h2-1.3.168.jar:1.3.168]
at org.h2.message.DbException.convert(DbException.java:281)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.Command.executeQuery(Command.java:195)
[h2-1.3.168.jar:1.3.168]
at
org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:109)
[h2-1.3.168.jar:1.3.168]
at
org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[rt.jar:1.6.0_27]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[rt.jar:1.6.0_27]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[rt.jar:1.6.0_27]
at java.lang.reflect.Method.invoke(Unknown Source) [rt.jar:1.6.0_27]
at
org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122)
[hibernate-core-4.1.6.Final.jar:4.1.6.Final]
... 105 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 0
at org.h2.index.PageDataLeaf.getRowAt(PageDataLeaf.java:327)
[h2-1.3.168.jar:1.3.168]
at org.h2.index.PageDataLeaf.getRowWithKey(PageDataLeaf.java:443)
[h2-1.3.168.jar:1.3.168]
at org.h2.index.PageDataNode.getRowWithKey(PageDataNode.java:270)
[h2-1.3.168.jar:1.3.168]
at org.h2.index.PageDataIndex.getRowWithKey(PageDataIndex.java:406)
[h2-1.3.168.jar:1.3.168]
at org.h2.index.PageDataIndex.getRow(PageDataIndex.java:395)
[h2-1.3.168.jar:1.3.168]
at org.h2.table.RegularTable.getRow(RegularTable.java:109)
[h2-1.3.168.jar:1.3.168]
at org.h2.index.PageBtreeIndex.getRow(PageBtreeIndex.java:295)
[h2-1.3.168.jar:1.3.168]
at org.h2.index.PageBtreeCursor.get(PageBtreeCursor.java:45)
[h2-1.3.168.jar:1.3.168]
at org.h2.index.IndexCursor.get(IndexCursor.java:223)
[h2-1.3.168.jar:1.3.168]
at org.h2.table.TableFilter.getValue(TableFilter.java:875)
[h2-1.3.168.jar:1.3.168]
at
org.h2.expression.ExpressionColumn.getValue(ExpressionColumn.java:175)
[h2-1.3.168.jar:1.3.168]
at org.h2.expression.ConditionIn.getValue(ConditionIn.java:44)
[h2-1.3.168.jar:1.3.168]
at org.h2.expression.ConditionAndOr.getValue(ConditionAndOr.java:83)
[h2-1.3.168.jar:1.3.168]
at org.h2.expression.ConditionAndOr.getValue(ConditionAndOr.java:83)
[h2-1.3.168.jar:1.3.168]
at org.h2.expression.Expression.getBooleanValue(Expression.java:180)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.dml.Select.queryFlat(Select.java:515)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.dml.Select.queryWithoutCache(Select.java:618)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.dml.Query.query(Query.java:307)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.dml.Query.query(Query.java:277)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.dml.Query.query(Query.java:36)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.CommandContainer.query(CommandContainer.java:86)
[h2-1.3.168.jar:1.3.168]
at org.h2.command.Command.executeQuery(Command.java:191)
[h2-1.3.168.jar:1.3.168]
... 112 more
--
You received this message because you are subscribed to the Google Groups H2
Database group.
To unsubscribe from this group and stop receiving emails from it, send an email
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For
Re: [h2] corrupt database 1.3.168
On 2013-08-13 10:05, Dieter Cailliau wrote: Here's another example of ArrayIndexOutOfBoundsException at org.h2.index.PageDataLeaf.getRowAt: this happened on 1.3.168. The most recent fix i found in changelog about this kind of error was 1.3.166, so probably there's still something wrong since then, or have there been fixes related to this, since 1.3.168? What does your database URL look like? -- You received this message because you are subscribed to the Google Groups H2 Database group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
