Hi Thomas, Thank you very much for the prompt response.
Actually, this issue is raised by my customer and I didn't get the database either. The database URL looks like below: jdbc:h2:/home/data/scm_activity.db I can't reproduce the problem. I wonder if this problem is caused by a corrupt database? I have received some bug reports from my customer which were caused by corrupt database (after running h2 recover tool, the problem dismissed). I do use multi-thread, some threads will read the data, and some will write the data. In my case, I use some lock mechanism by myself to isolate the operation to database. That is, every time multiple threads can open the database for reading which will block the write thread, and only one thread can open the database for writing which will block all other threads. When a thread want to access the database for read, below url is used: jdbc:h2:/home/data/scm_activity.db;ACCESS_MODE_DATA=r So, would you please give some suggestions or direction on this? By the way, I can't use h2 in server mode as there may be too much data need be stored. Best Regards Steve On Feb 4, 4:29 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > I don't know what it could be. I wonder if it could be a > multi-threading issue... > > Could you send me the database file? > > If not, what is your database URL? Do you have a reproducible test case? > > Regards, > Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
