On 1/21/16, Daniel Polski <daniel at agelektronik.se> wrote: > Hello, > > I have a problem getting SQLITE_BUSY, and the lock won?t get released. > > We haven't been able to reproduce the locking ourselves even when trying > to stress test the system, but have received several error reports from > customers describing the same situation.
That's frustrating. There's nothing that is harder to fix that something that always works. > > Any suggestions how to debug and find the reason why we get SQLITE_BUSY? Have you enabled error and warning logging? https://www.sqlite.org/errlog.html Can you enhance your existing log to report the sqlite3_extended_errcode() value in addition to the basic error code? -- D. Richard Hipp drh at sqlite.org
