Hi Using 1.4.199. New database just two weeks old, running in Jetty web application. I was the only user working on it, deleting a few dozen image blobs one by one via the webapp.
My application apparently has a memory leak, so when I tried to delete another image, an OutOfMemoryError happened (actually this was already the 2nd out-of-memory, but in the previous instance the db did not get corrupted, and I was able to just reboot the server). I am pretty sure that the only write statement in progress at that moment could have been "DELETE FROM my_attachments_table WHERE id=?". Inside a transaction, with LOCK_MODE=1. Now the database is corrupted and the Recover tool also throws an exception. Am I already out of options? :( (frustration rant of the moment: H2 database corruption just happens way too often in my experience, which is a real pity, because I love H2) Reto -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/ae7fcfcc-9b74-437d-9639-613758c0857a%40googlegroups.com.
