[h2] org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[5528] data leaf table

2013-09-06 Thread Sanjeev Gour
Recently we saw the "data leaf table" related error in our environment and not sure what could have cause it. We are using the following options- * DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=1;CACHE_SIZE=131072;CACHE_TYPE=SOFT_LRU;MVCC=TRUE * We are using it under JBoss and due to this error the JB

[h2] Re: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[5528] data leaf table

2013-09-06 Thread Sanjeev Gour
Update: We are using version 1.3.168. On Friday, 6 September 2013 12:51:20 UTC+5:30, Sanjeev Gour wrote: > > Recently we saw the "data leaf table" related error in our environment and > not sure what could have cause it. We are using the following options- > > *

Re: [h2] Re: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[5528] data leaf table

2013-09-06 Thread Sanjeev Gour
gt; > In particular, MVCC is still a little bit experimental. > It works for some people, but not for others, and we're no longer actively > working on the feature, so your chances of a bugfix are slim. > > > On 2013-09-06 09:26, Sanjeev Gour wrote: > > Update: We are usi

Re: [h2] Re: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[5528] data leaf table

2013-09-06 Thread Sanjeev Gour
Ok, we shall try removing that to avoid even a rare case of databacse corruption. On Sep 6, 2013 3:19 PM, "Noel Grandin" wrote: > > On 2013-09-06 11:43, Sanjeev Gour wrote: > >> >> (2) turn off MVCC - Would it cause the read/write to the database to >&g

Re: [h2] Re: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[5528] data leaf table

2014-06-26 Thread Sanjeev Gour
Here it is- Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[30284] data node table:167 entries:168 [1438, 1437, 2679, 2706, 2709, 2711, 2713, 2716, 3690, 3706, 3709, 4481, 12184, 16323, 16364, 16368, 16370, 16372, 16528, 16531, 16545, 16547, 16601, 16604,

[h2] pageStore: Transaction log could not be truncated - anything to worry about?

2014-08-11 Thread Sanjeev Gour
Hello- I see in my application that this message is sometime printed in the trace file. I see a related post to this message but I am unsure if it is really a problem or an informational message. Is there any important info that I lose when this message is printed? This is the related post- ht

Re: [h2] pageStore: Transaction log could not be truncated - anything to worry about?

2014-09-15 Thread Sanjeev Gour
there is no such transaction > (meaning that the message is sometimes logged in error). > > What you should check is if you do have a long running transaction, as in > general this should be avoided. But no data is lost. > > Regards, > Thomas > > > On Mon, Aug 11, 201

NPE when shutting H2 down after integration tests run

2012-09-18 Thread Sanjeev Gour
On out build system, we have seen this error a couple of time when shutting H2 down after integration tests run, has anyone seen this before and knows what could be causing it? org.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException"; SQL statement: SHUTDOWN [5-162] org

NPE when shutting H2 down after integration tests run

2012-09-19 Thread Sanjeev Gour
We have been seeing this exception sometimes when the integration test run completes and an attempt is made to shutdown the H2. Has anyone seen this before and knows what could be going wrong? org.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException"; SQL statement: SHUTDOWN

Re: NPE when shutting H2 down after integration tests run

2012-09-26 Thread Sanjeev Gour
We haven't tested that yet. We are using 1.3.162 currently and upgrading to 1.3.169. We will keep an eye if it happen with the latest version. Thanks. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit htt

"org.h2.jdbc.JdbcSQLException: Row not found when trying to delete from index" with Version 1.3.162

2013-05-13 Thread Sanjeev Gour
I am getting the following error when running a clean up routine on some of the tables. I am using version 1.3.162. The JDBC url is configured with the following options- CACHE_TYPE=LRU;PAGE_SIZE=16384;MVCC=TRUE;DB_CLOSE_DELAY=-1 Also tried with ";optimize_update=false" to no avail. This typic

Re: "org.h2.jdbc.JdbcSQLException: Row not found when trying to delete from index" with Version 1.3.162

2013-05-13 Thread Sanjeev Gour
around the edges. > > On 2013-05-13 14:47, Sanjeev Gour wrote: > > I am getting the following error when running a clean up routine on some > of the tables. I am using version 1.3.162. The JDBC url is configured with > the following options- > > CACHE_TYPE=LRU;PAG

Problem with dropping and recreating index

2013-05-22 Thread Sanjeev Gour
We are having an index on a table that results in error while deleting data from the table. The error says that it cannot find a row in the index. The following discussion we posted earlier has detailed explanation about it- Discussion link

Re: "org.h2.jdbc.JdbcSQLException: Row not found when trying to delete from index" with Version 1.3.162

2013-05-30 Thread Sanjeev Gour
We have tried this with the latest build but that did not solve the problem for us. Any other advice on this one? On Tuesday, 14 May 2013 10:51:06 UTC+5:30, Sanjeev Gour wrote: > > Sorry, I mentioned the incorrect version number, I am using *1.3.168*. > Earlier we also tried without

[h2] Re: "org.h2.jdbc.JdbcSQLException: Row not found when trying to delete from index" with Version 1.3.162

2013-06-05 Thread Sanjeev Gour
ot;runscript". > > Regards, > Thomas > > > On Thursday, May 30, 2013, Sanjeev Gour wrote: > >> We have tried this with the latest build but that did not solve the >> problem for us. Any other advice on this one? >> >> On Tuesday, 14 May 2013 10:51:06

Re: [h2] Re: Problem with dropping and recreating index

2013-06-13 Thread Sanjeev Gour
uces the corrupt index > (starting with a fresh database) with the latest version of H2, could you > please post it? > > Regards, > Thomas > > > On Wed, May 22, 2013 at 5:30 PM, Sanjeev Gour wrote: > >> We are having an index on a table that results in error while deletin