On 17 Jul 2014, at 10:10am, Micka <mickamus...@gmail.com> wrote: > Well, > > All of my process are using Mutex to protect sqlite from concurrent access. > > That why I don't understand why I get SQLITE_BUSY error . > > Micka, > > > On Tue, Jul 8, 2014 at 11:44 PM, Simon Slavin <slav...@bigfraud.org> wrote: > >> Have you set a timeout
Did you set a timeout period for that connection ? If you didn't set a timeout, then the database API call will try once to open the file, find that it has a MUTEX lock, and fail, giving you SQLITE_BUSY. If you do set a timeout, then the database API call will try once to open the file, find that it has a MUTEX lock, and keep checking the lock until your timeout period has passed. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
