View Ticket
Not logged in
Ticket UUID: fbd3d93d98c2601935a30e3ad1416153b149072d
Title: Error "database is locked" seen via log callback
Status: Closed Type: Incident
Severity: Important Priority: Medium
Subsystem: Integration_Via_PInvoke Resolution: Works_As_Designed
Last Modified: 2018-08-10 18:01:15
Version Found In:
User Comments:
anonymous added on 2018-07-02 08:41:29: (text/x-fossil-plain)
Reasonly, we have updated our version to 1.0.107. and now, we are experiencing "System.Data.SQLite.SQLiteLog.LogCallback: SQLite error (5): database is locked" several times in our trace log. (we have implemented the custom trace log listener). we close the every connection after it opens. Even though above log is written, database connection is open successfully and no exception is thrown. but we would like to know the reason behind it.

Further more, we added Thread.Sleep(100); before call the method and then we did not notice above error in our trace log. It seems sqllite take some time to release the sqlite file after connection is closed ?


what is the reason for this error ? 
Can we ignore this error log ?

mistachkin added on 2018-07-04 17:46:33: (text/x-fossil-plain)
Do you know the SQL statement(s) that are causing this error to be logged?  Are
any exceptions being thrown?

anonymous added on 2018-07-06 03:44:16: (text/x-fossil-plain)
This log, I have seen when calling and no exception will be thrown.

mistachkin added on 2018-07-06 04:01:52: (text/x-fossil-plain)
Generally speaking, these types of log messages are harmless if no exception is
seen by your code.

However, I may be incorrect.  If you show some C# sample code that demonstrates
the issue, I can perform a more detailed analysis of the situation.

anonymous added on 2018-08-09 08:31:19: (text/x-fossil-plain)
If we've determined that the messages are harmless for us.

Is it possible to configure System.Data.SQLite to stop writing the error to our output?

mistachkin added on 2018-08-10 18:01:15: (text/x-fossil-plain)
If you are implementing a custom logging callback, you can perform custom
filtering there; the default logging callback does not filter messages.