[h2] No database in the Console

2015-03-04 Thread Thomas Mueller
Hi, Well, if the error message really is exactly this, then for some reason the database URL in the code itself is an empty string (you can't always thrust what is in the GUI). You may want to debug. Regards, Thomas On Wed, Mar 4, 2015 at 12:20 PM, Max Telfer wrote: > Hi again > > The URL a

Re: [h2] MVStore.cacheChunkRef memory usage

2015-03-04 Thread Thomas Mueller
Hi, I have a new patch for the LIRS cache: Index: src/main/org/h2/mvstore/cache/CacheLongKeyLIRS.java === --- src/main/org/h2/mvstore/cache/CacheLongKeyLIRS.java (revision 6051) +++ src/main/org/h2/mvstore/cache/CacheLongKeyLIRS.java

Re: [h2] No database in the Console

2015-03-04 Thread Noel Grandin
What browser are you using? Do you perhaps have some nasty browser plugins installed? -- 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...@goog

Re: [h2] file corrupted

2015-03-04 Thread Noel Grandin
Hi I am sorry but your database is corrupt. All that you can do is to either restore from a backup, or try running the Recover tool, but the Recover tool is not guaranteed to restore all of your data. -- Noel -- You received this message because you are subscribed to the Google Groups "H2 Data

Re: [h2] Deadlock caused by h2 disk access

2015-03-04 Thread Noel Grandin
Hi Our performance tuning guide is here: http://h2database.com/html/performance.html 2GB is not that big a database. Based on your thread dump I suspect that you are DOSing yourself. What I think is happening is that you have some task that executes periodically. Sometimes the task takes too lon

Re: [h2] Deadlock caused by h2 disk access

2015-03-04 Thread Duc Nguyen
Hi Grandin, Thanks for your hint about slow query issue. We have observed lots of query with query time over 30 mins, which is extremely slow, and our application's performance is greatly compacted. Currently the database size is over 2GB, could that be the cause? Please give hint on how can us

Re: [h2] file corrupted

2015-03-04 Thread Ryan How
Heya, What's your connection string? On 5/03/2015 8:16 AM, Bashorun Olajide wrote: i am new to H2, i just started 2 days ago after reading about javafx. i got an error while trying to retrieve record in a database. i dont even know maybe successfully connection established. i got this error

[h2] file corrupted

2015-03-04 Thread Bashorun Olajide
i am new to H2, i just started 2 days ago after reading about javafx. i got an error while trying to retrieve record in a database. i dont even know maybe successfully connection established. i got this error org.h2.jdbcSQLException: File corrupted while reading record:"[6] stream data key:1 pos

Re: SOLVED - [h2] Re: Connection error - H2 Database Engine: New version 1.4.186

2015-03-04 Thread Antonio Monforte
Hi, *SOLVED* restoring a backup of database. Regards *António Monforte* quarta-feira, 4 de Março de 2015 às 06:43:27 UTC, Thomas Mueller escreveu: > > Hi, > > Does it work if you open the database with an older version of H2? > > Regards, > Thomas > > On Tuesday, March 3, 2015, Noel Grandin >

Re: [h2] MVStore.cacheChunkRef memory usage

2015-03-04 Thread Thomas Mueller
Hi, Thanks a lot for the test cases and the patch! I'm still trying to understand the patch, and I am trying to find a simpler way to fix the problem. Regards, Thomas On Sunday, March 1, 2015, Fred&Dani&Pandora&Aquiles wrote: > Hi Thomas, > > I attached a patch that reproduces the problem and

Re: [h2] No database in the Console

2015-03-04 Thread Max Telfer
Hi again The URL and Console fields are in the original post. What should it be? Thanks Max On Wednesday, March 4, 2015 at 5:43:31 PM UTC+11, Thomas Mueller wrote: > > Hi, > > If the message is really > > java.sql.SQLException: No suitable driver found for > at java.sql.DriverManager.

Re: [h2] Deadlock caused by h2 disk access

2015-03-04 Thread Noel Grandin
That's not a deadlock, that's just a slow SQL command that is causing your other SQL commands to back up. There is no cure for this beyond performance tuning. Also your thread pool implementation does not seem to be doing it's job of limiting the number of active threads properly, since you ha