They're all being accessed from multiple threads within a single process app, with no external sources/connections. This happens on both OSX and Win32. Always on a local disk.
I'm using the release amalg straight off the website (3.7.17), with SQLITE_ENABLE_FTS3/FTS3_PARENTHESIS as preprocessor options. The database is fine when you restart the app -- it just seems to hit the locked error once in a blue moon, which I have set up to assert out right now to help me track it down. -David -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin Sent: Friday, July 26, 2013 5:53 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Any way to debug database is locked? On 27 Jul 2013, at 1:20am, David de Regt <dav...@mylollc.com> wrote: > Is there any chance that the OS is still flushing the WAL changes to disk > post-closing the database in another connection, when another connection > tries to get an exclusive lock? How are your various processes contacting the database file ? Are they all running on the computer the database is kept on ? Or are they using network access ? If so, which NFS ? Which pragmas have you used ? Does your database pass the integrity check ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
