[h2] Re: Exclusive mode behavior change from 1.4.199 to 1.4.200

Awesome, man. Thank you! I've previously submitted H2 code contributions. Feel free to incorporate the unit tests as you see fit. On Wednesday, October 16, 2019 at 3:44:48 PM UTC-5, Andrei Tokar wrote: > > I won't even try to defend this one. It is a bug, and fix is here. >

[h2] Re: Exclusive mode behavior change from 1.4.199 to 1.4.200

I won't even try to defend this one. It is a bug, and fix is here. -- 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

[h2] 200 crash issue

Hello, It looks like there is an intermittent bug lurking in 1.4.200. This occured on a freshly created database during data import performed by a higher-level routine (i.e. not a H2's RUNSCRIPT). The progress of the import at the time of crash was around 3.5%:

[h2] Re: Exclusive mode behavior change from 1.4.199 to 1.4.200

Andrei- Thank you for the quick response. Can you elaborate on the thought process about why going from 1 to 2 would throw the same error? Prior to 1.4.200 we used a progression of EXCLUSIVE settings: a. Don't allow new connections (ie allow connections to natural quiesce) SET EXCLUSIVE 1

[h2] Re: Exclusive mode behavior change from 1.4.199 to 1.4.200

Although it is a departure from a previous behavior, this is expected, because documentation says: Only the connection that set the exclusive mode can disable it At the point when test fails, exclusive mode is not set (or rather unset

[h2] Exclusive mode behavior change from 1.4.199 to 1.4.200

With 1.4.200 we noticed that the Exclusive Mode handling changed a bit. A grep of the Change Log didn't bubble anything up. The behavior now indicates that Exclusive Mode must always go from 0 to 1,2 or 1,2 to 0. // 1.4.199 SET EXCLUSIVE 0 SET EXCLUSIVE 0 <-- no exception SET EXCLUSIVE 1

Re: [h2] Self-test?

On Wed, 16 Oct 2019, Noel Grandin wrote: > that is some kind of corruption being triggered during the compact phase when > the db closes. > > you could work around that by disabling compaction, by appending > ";MAX_COMPACT_TIME=0" to the connection URL OWASP people, can you do something with

Re: [h2] Self-test?

that is some kind of corruption being triggered during the compact phase when the db closes. you could work around that by disabling compaction, by appending ";MAX_COMPACT_TIME=0" to the connection URL -- You received this message because you are subscribed to the Google Groups "H2

Re: [h2] Self-test?

On Wed, 16 Oct 2019, Thorsten Glaser wrote: > tl;dr: I’m getting “Unable to connect to the database” after it was created, I’ve discovered some more log: ~/.m2/repository/org/owasp/dependency-check-data/4.0/odc.trace.db -BEGIN cutting here may damage your screen surface- 2019-10-16

Re: [h2] Self-test?

On Wed, 16 Oct 2019, Noel Grandin wrote: > THe emulated part is possibly the problem - some filesystem related thing is > re-using inode-no/device-no pairs Yes, I read this from the SMB reference, but this cannot happen in this scenatio: from the operating system’s point of view, it’s like a

Re: [h2] Self-test?

… this storage is not virtualised like in the Docker/cloud scenario: it’s an emulated hard disc drive, on which a normal ext4 filesystem is used locally. THe emulated part is possibly the problem - some filesystem related thing is re-using inode-no/device-no pairs, which appears to

Re: [h2] Self-test?

On Wed, 16 Oct 2019, Noel Grandin wrote: > looks very similar to > >https://github.com/h2database/h2database/issues/2152 Hmm, no… lsof shows nothing is keeping the file open, and… > so probably java is not liking virtualised storage for some reason … this storage is not virtualised like

Re: [h2] Self-test?

looks very similar to https://github.com/h2database/h2database/issues/2152 so probably java is not liking virtualised storage for some reason -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving

[h2] Self-test?

Hi *, I’m running into a problem with a Maven plugin that uses the H2 database: https://github.com/jeremylong/DependencyCheck/issues/2262 tl;dr: I’m getting “Unable to connect to the database” after it was created, upstream says something about it being locked, and it’s massively larger than

[h2] Re: Can't create full text index (H2: v1.4.200 , lucene: v7.7.2 or v8.2.0)

Yes. 5.5.5 is normal. On Wednesday, October 16, 2019 at 4:37:56 PM UTC+8, Evgenij Ryazanov wrote: > > The situation is even worse, the binary compatibility with 6 is broken too. > > So you need to use 5.5.5 (it was used for compilation of official release > of H2 1.4.200), or you can build H2

[h2] Re: Can't create full text index (H2: v1.4.200 , lucene: v7.7.2 or v8.2.0)

The situation is even worse, the binary compatibility with 6 is broken too. So you need to use 5.5.5 (it was used for compilation of official release of H2 1.4.200), or you can build H2 from its current sources if you definitely need a newer version of Lucene for a some reason. -- You

[h2] Re: Can't create full text index (H2: v1.4.200 , lucene: v7.7.2 or v8.2.0)

Return to Lucene 6.6.6. I get this: CALL FTL_CREATE_INDEX('PUBLIC', 'TEST', 'FIRST_NAME,LAST_NAME'); Exception calling user-defined function: "createIndex(conn2: url=jdbc:default:connection user=SA, PUBLIC, TEST, FIRST_NAME,LAST_NAME): org.apache.lucene.index.IndexWriter.commit()V"; SQL

[h2] Re: Can't create full text index (H2: v1.4.200 , lucene: v7.7.2 or v8.2.0)

Oh, I see. We definitely have a problem. Try some older version of Lucene such as 6.6.*. 7.0.0 and newer versions are source compatible but binary incompatible, if you need them, you need to recompile H2 with that version. I'll try to fix the binary compatibility for a next version of H2. I

[h2] Re: Can't create full text index (H2: v1.4.200 , lucene: v7.7.2 or v8.2.0)

I'm sure that all lucene-related jars are in the classpath. Stack trace is below. But I don't know how to figure it. CALL FTL_CREATE_INDEX('PUBLIC', 'TEST', 'FIRST_NAME,LAST_NAME'); Error creating or initializing trigger "FTL_TEST" object, class