Re: [h2] ArrayIndexOutOfBoundsException with multiple Threads using h2-1.3.176

I have seen this on 1.3.175 in the customer's logs. Config: MVCC=TRUE;MULTI_THREADED=0;LOCK_MODE=3;LOCK_TIMEOUT=2; Here's a stacktrace: 2016-07-25T17:09:43,158 [ERROR][System.err] Caused by: org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.IOException:

Re: [h2] Unique index or primary key violation: SYS_ID ON PUBLIC.SYS(ID) [23505-168] (using 1.3.168)

Same problem. 1. The database was created in CREATE_BUILD 170, then was used with 1.3.174. I've tried using 1.4.178 on that database in Hibernate-based product - got org.h2.jdbc.JdbcSQLException: Unique index or primary key violation: PRIMARY KEY ON .PAGE_INDEX; SQL statement:[...] 1.3.175

[h2] Re: Concurrent operations on LOBs

I can say that the approach with VARCHARs works ok in my case after several months of test/production usage. I'm using up to 10K length VARCHARs. On Tuesday, March 5, 2013 2:18:21 AM UTC+2, Kartweel wrote: It depends on your use case I think. I recently had 10MB objects reading into

Re: Concurrent operations on LOBs

if I'm not mistaken?. How big are your BLOBS? On 1/03/2013 8:30 AM, Nick99 wrote: Hello, Any plans for the fix/workaround? I can only think of some pretty messy workarounds like moving my CLOB fields to a) just VARCHAR(*255*) /though the docs say *The maximum precision

Re: Concurrent operations on LOBs

behave the same way as CLOB) c) or to BINARY (looks promising). On Tuesday, December 4, 2012 6:59:08 PM UTC+2, Nick99 wrote: It seems the problem is with MVCC. The test is not failing for 30s on my system with: jdbc:h2:db/test01;MVCC= *FALSE*;MULTI_THREADED=0;LOCK_MODE=3;LOCK_TIMEOUT=2

Re: Concurrent operations on LOBs

It seems the problem is with MVCC. The test is not failing for 30s on my system with: jdbc:h2:db/test01;MVCC=* FALSE*;MULTI_THREADED=0;LOCK_MODE=3;LOCK_TIMEOUT=2; All isolation levels fail for (in the 1-5s timeframe): jdbc:h2:db/test01;MVCC=*TRUE;*

Re: Concurrent operations on LOBs

). For that reason, we use SimpleORM as our mapping layer to the database. On 2012-11-16 22:33, Nick99 wrote: Okay, it seems I've isolated the source of missing lobs/LOB NPEs/missing lob entry problems. At this point I cannot attach a compilable project, just the test code and the trace log

Re: Missing Lob Entry

I can try to provide the info, if needed ;) (here https://groups.google.com/d/msg/h2-database/LuYRx84vFIc/d9jyaefh7XsJ) On Friday, August 31, 2012 6:35:51 PM UTC+3, Thomas Mueller wrote: Hi, I'm sorry for the delay. This looks like a corrupt database. To recover the data, use the tool

Re: Concurrent operations on LOBs

at 4:50 PM, Nick99 nail.a...@gmail.com javascript: wrote: hi, I think I bumped into a similar bug. I have a multithreaded app; an instance of some class is updated; then it is loaded and an NPE is thrown by H2. I use #169, Windows 7, NTFS. I cannot provide a test case at the moment; nor

Re: Concurrent operations on LOBs

The resultset returned by com.mchange.v2.c3p0.impl.NewProxyPreparedStatement public final java.sql.ResultSet executeQuery() throws java.sql.SQLException { /* compiled code */ } has - currentRow = {org.h2.value.Value[125]@13167} - [0] = {org.h2.value.ValueLong@13177}34 - [1] =

Re: Concurrent operations on LOBs

hi, I think I bumped into a similar bug. I have a multithreaded app; an instance of some class is updated; then it is loaded and an NPE is thrown by H2. I use #169, Windows 7, NTFS. I cannot provide a test case at the moment; nor can I reproduce it again. Could you please look what can be

ALTER TABLE ... DROP COLUMN IF EXISTS misbehaves?

Hi, H2 1.3.157 I'm trying to drop a column /via console/ if it exists: ALTER TABLE TEST DROP COLUMN IF EXISTS 'UUID' Column IF not found; SQL statement: ALTER TABLE TEST DROP COLUMN IF EXISTS 'UUID' [42122-154] 42S22/42122 (Help) however,