Re: [h2] Exception when opening DB after forced shutdown (1.3.176)

2014-06-10 Thread Thomas Mueller
Hi, You could use version 1.4.178, and append ;mv_store=false to the database URL. This will disable the MVStore file format. Also my jUnit tests failed with inability to create in-memory DB because of missing driver (for jdbc:h2:mem:). not sure whether I'd have to load driver class explicitly

Re: [h2] Exception when opening DB after forced shutdown (1.3.176)

2014-06-05 Thread too
Hi, I tested with the 1.3.178 and I can confirm that it resolved problem. Tried twice with new jar and problem has not occurred, then tried back with 1.3.176 and replicated it immediately. With damaged DB then tried the new jar and it recovered just fine. I consider this fixed now, thank you!

Re: [h2] Exception when opening DB after forced shutdown (1.3.176)

2014-06-05 Thread too
I just noticed the version is 1.4.178, not 1.3.x.. I will need to wait for stable release then before I can use the jar Also my jUnit tests failed with inability to create in-memory DB because of missing driver (for jdbc:h2:mem:). not sure whether I'd have to load driver class explicitly for

Re: [h2] Exception when opening DB after forced shutdown (1.3.176)

2014-06-04 Thread Thomas Mueller
Hi, The latest build is available at: http://h2database.com/html/build.html#automated Can you point me in some direction as what to look for? If you don't create temporary tables, then most likely the problem is large result sets, as in some cases this will implicitly create temporary tables.

Re: [h2] Exception when opening DB after forced shutdown (1.3.176)

2014-06-03 Thread too
Hello, I can test the fix for you easily, all I need is h2 jar with fix. Regarding the test I tried all I could think of. Our app is fairly large (15MB jar of classes with lots of framework-ish stuff happening in the background) so it is difficult to point out the scenario. Tried INFO logging

Re: [h2] Exception when opening DB after forced shutdown (1.3.176)

2014-06-02 Thread Thomas Mueller
Hi, I could analyze it now. The problem seems to be that creating a temporary table is not committed, and then the temporary table is deleted in another session. I have a fix / workaround for that, but so far no test case. Please tell me if you have a reproducible test case. Regards, Thomas

Re: [h2] Exception when opening DB after forced shutdown (1.3.176)

2014-05-22 Thread Thomas Mueller
Hi, I would need a reproducible test case. Regards, Thomas On Tuesday, May 20, 2014, too tono...@gmail.com wrote: Hi, Sometimes when our application is shut down forcibly it is unable to start again with exceptions below. It does not appear that transaction is in progress at the time of