As a first step, update to the latest release H2 jar (1.3.176) or the latest beta jar (1.4.192).
As a second step, try to find reliable steps to reproduce the problem. This helps fix the problem. On Friday, 24 June 2016 09:26:43 UTC+2, Ranjit K wrote: > > My question to you more specifically is “how to do we prevent H2 DB or > tables from getting corrupt?” > > > > We think that since the connection to database is getting closed abruptly, > it might be causing the following SELECT query to fail (which can possibly > be due to database/table corruption). > > On Friday, 24 June 2016 01:34:56 UTC+5:30, Ranjit K wrote: >> >> What are the reasons H2 database can get corrupted? Is it possible that >> the 1st exception is the reason behind 2nd exception? >> >> On Thursday, 23 June 2016 21:52:10 UTC+5:30, Noel Grandin wrote: >>> >>> The first exception is occurring because somewhere your code is >>> forgetting to close a java.sql.Connection >>> >>> The second exception is occurring because your DB has become corrupted. >>> >>> >> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
