Hi, I see a interesting behavior using FILE_LOCK=SOCKET during development. Sometimes I shutdown the application and it´s possible to see that socket used as lock no longer exists:
netstat -an | fin /i "3405" Nevertheless my application refuses to start with following error: org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked by another computer: 10.0.6.102". It´s easy to solve this issue, just delete *data.lock.db *and the application starts normally. I choose socket lock since there´s only one application which access the database and according to docs this method avoid polling lock file. According to H2 docs, it should delete the file lock automatically when socket port was released: *"**If the lock file exists, and the lock method is 'socket', then the process checks if the port is in use. If the original process is still running, the port is in use and this process throws an exception (database is in use). If the original process died (for example due to a power failure, or abnormal termination of the virtual machine), then the port was released. The new process deletes the lock file and starts again."* Thanks in advance. -- Márcio Geovani Jasinski Blumenau, Santa Catarina Fone: +55 47 9653 4899 -- 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.
