Re: [h2] Proliferation of undroppable SEQUENCES

2013-09-30 Thread Noel Grandin
I don't think there is much that you can do short of doing a SCRIPT and RUNSCRIPT cycle. You don't perhaps create temporary tables somewhere in your app? That's the only thing I can think of that might lead to a situation with that many sequences. Doing a backup to script and then grepping

[h2] Re: unable to write: the database is read only after system crash

2013-09-30 Thread Dieter Cailliau
I'm using h2-1.3.168 in jboss 7.2.0.Final on a Win7. -- 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 email to h2-database+unsubscr...@googlegroups.com. To post to this

Re: [h2] unable to write: the database is read only after system crash

2013-09-30 Thread Noel Grandin
What exactly does the trace file say the problem is? Also, this DB is working for me on the latest version. Which may mean that the problem has been fixed, but might also just be that something in your local environment, which is different to me, is triggering the problem. On 2013-09-30

Re: [h2] unable to write: the database is read only after system crash

2013-09-30 Thread Dieter Cailliau
Every insert gives this in bms.trace.db org.h2.jdbc.JdbcSQLException: The database is read only; SQL statement: insert into Element (lastSeen, sources, name, options, tupple, host_string, assets2, DTYPE, string) values (?, ?, ?, ?, ?, ?, ?, 'DeviceCapabilityService', ?) [90097-168]^M at

[h2] Stall using MVCC

2013-09-30 Thread Rui Vilão
Hi all, My application is stalling when using MVCC. I'm using the 1.3.173 version embedded in another application. I was able to reproduce the exact same behaviour with 1.3.164 but analysing the thread dump using that version it seemed to me that it was a deadlock. With the most recent

Re: [h2] Stall using MVCC

2013-09-30 Thread Noel Grandin
MVCC has various issues. Some people use it successfully, for others it doesn't work so well. The basic advice, for now, is don't use it if it causes you problems. We're not going to work on fixing any bugs in MVCC itself because Thomas is working on a replacement engine which does MVCC

Re: [h2] unable to write: the database is read only after system crash

2013-09-30 Thread Noel Grandin
Hi I'm sorry, at this I've reached the limit of my knowledge of that area of the engine. Hopefully Thomas will chime in. Is it indeed a problem in database recovery. I can tell is that it the DB is being set readonly by the following logic in PageStore.recover() if

Re: [h2] Stall using MVCC

2013-09-30 Thread Rui Vilão
Hi, Thank you for the quick reply. Do you have a date for that release already? Thanks,  Rui On Mon, Sep 30, 2013 at 12:46 PM, Noel Grandin noelgran...@gmail.com wrote: MVCC has various issues. Some people use it successfully, for others it doesn't work so well. The basic advice,

Re: [h2] Stall using MVCC

2013-09-30 Thread Noel Grandin
Thomas is working on it in his spare time, so pretty much sometime in the next year or so On 2013-09-30 13:56, Rui Vilão wrote: Hi, Thank you for the quick reply. Do you have a date for that release already? Thanks, Rui On Mon, Sep 30, 2013 at 12:46 PM, Noel Grandin

Re: [h2] Stall using MVCC

2013-09-30 Thread Rui Vilão
Right thanks. Rui On Mon, Sep 30, 2013 at 12:57 PM, Noel Grandin noelgran...@gmail.com wrote: Thomas is working on it in his spare time, so pretty much sometime in the next year or so On 2013-09-30 13:56, Rui Vilão wrote: Hi, Thank you for the quick reply. Do you have a date for that

Re: [h2] Parameter Handling Bug

2013-09-30 Thread Mike Goodwin
Hi, Ok sorry. I thought possibly it would be relatively easy to debug if you could see it happening. I can certainly create the test as a standalone stored procedure, and then I suppose I should have a go at removing bits to try and reduce it. In terms of h2 code is there a reason that the

Re: [h2] Parameter Handling Bug

2013-09-30 Thread Noel Grandin
On 2013-09-30 14:16, Mike Goodwin wrote: In terms of h2 code is there a reason that the parameter references need to be copied in the manner that they are? In my simplistic understanding for a given stored procedure there will always be a fixed number of parameters, so in an ideal world a