If you start and stop the database in quick succession (as will happen for a set of unit tests) then depending on the timing the next start will see the lock file as recently modified. I have seen it a couple of times if I start a unit test run, cancel it and start the run again. I am not sure why this check is being done. Thomas, should be able to tell you exactly what the behaviour is.
Donal. On Aug 23, 4:06 pm, Ayelet <[email protected]> wrote: > Hi, > > We're using the database in client-server mode, and recently got this > error (while running unit tests that are single threaded): > Error opening database: "Lock file recently modified" [8000-128] > > We weren't able to reproduce this, but would still like to get to the > bottom of it. > > Any ideas? > > Thanks, > Ayelet -- 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.
