Re: [h2] shared read lock messages

Hi Yeah, that's a trace message. But you should only be seeing those if you have the set trace level to DEBUG. http://h2database.com/html/features.html#trace_options -- Noel On 2014-03-14 20:15, Brian Craft wrote: shared read lock requesting for -- You received this message because you are

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

With 1.3.175 the error message is a bit longer: Uniqhttp://127.0.1.1:8082/test.do?jsessionid=4ea64ad64b043f1dd5de67ef7339a197#ue index or primary key violation: SYS_ID ON PUBLIC.SYS(ID) VALUES ( /* key:266 */ 15, 0, 3, 'CREATE SEQUENCE

Re: [h2] DB growth when using TEMPORARY TABLE NOT PERSISTENT?

Hi Thanks for the test case. This is my analysis so far. I won't have time to implement a fix right now, but maybe someone else will. Basically, we are leaking temporary tables. Uli, you can probably work around this by increasing the MAX_MEMORY_ROWS_DISTINCT parameter. LocalResult is

Re: [h2] DB growth when using TEMPORARY TABLE NOT PERSISTENT?

Hi Noel, thanks for analysing it! At the moment I can live with the workaround (increasing MAX_MEMORY_ROWS_DISTINCT). Anyhow it would be nice if this becomes fixed :-) Thanks for your good work!! Uli -- You received this message because you are subscribed to the Google Groups H2 Database

Re: [h2] Blocking issue: Sequence issue with 1.3.175 due to MINVALUE =1 and START VALUE 0 while created with H2 1.3.175 (so no MINIVALUE at creation)

I tested with the DB you sent and I'm not seeing any exception at all on startup. I'm sorry, I have no idea how you are triggering this problem. The only thing I can think of is that you have weird code somewhere that is fiddling with the cluster settings. Maybe in one of your libraries? On

Re: [h2] Blocking issue: Sequence issue with 1.3.175 due to MINVALUE =1 and START VALUE 0 while created with H2 1.3.175 (so no MINIVALUE at creation)

Hi Noel, Thank you for your time and tries ! I don't have any idea of what happened, but still here is my situation (last week-end, I've done several tests too): 1) one database created a long time ago (probably 2 years ago), upgraded from time to time until version 174 has an issue with this

[h2] java.lang.RuntimeException - 50000-175

I am randomly getting RuntimeException when I am loading data through table link. (Note: loading multiple tables concurrently) I am using h2-1.3.175.jar and had issue with previous release too. Does anyone had issue? any help will be appreciated. General error: java.lang.RuntimeException:

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

Hi, Could you tell us, what database URL do you or did you use? It looks like a corruption of some kind, but I'm not sure. Regards, Thomas On Mon, Mar 17, 2014 at 8:11 AM, Dieter Cailliau dieter.caill...@gmail.comwrote: With 1.3.175 the error message is a bit longer:

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

Hi, Some more questions: - With which version of H2 was this database created? You can find it out using: select * from information_schema.settings where name='CREATE_BUILD' or have a look in the SQL script created by the recover tool. - Did the application run out of memory (once,

Re: [h2] java.lang.RuntimeException - 50000-175

Hi, Could you tell us what database URL you are using, and post the complete stack trace please? Regards, Thomas On Tue, Mar 18, 2014 at 5:58 AM, Vishwanatha Sundarappa vishwas...@gmail.com wrote: I am randomly getting RuntimeException when I am loading data through table link. (Note: