That's not how you set a busy timeout using a connection string. That's not how you set any (pragma) options with a connection string. Check the System.Data.SQLite documentation (or google) to find out connection string parameters, or play around with the SQLiteConnectionStringBuilder.
The busy timeout pragma will not help if you end up in a deadlock. One way a deadlock can occur is as follows: 1) Connection A starts a transaction and reads the database - it takes out a shared lock 2) Connection B starts a transaction and reads the database - it too takes out a shared lock 3) Connection A attempts to write to the database, so it upgrades to a reserved lock and waits for all readers to close (all shared locks to be released). 4) Connection B attempts to write to the database. It keeps its shared lock and tries to upgrade to reserved. Because A already owns a reserved lock, connection B is denied its lock. No amount of waiting will solve this problem because A is waiting for B to release its lock so it can have an exclusive lock. SQLite knows this, so it returns SQLITE_BUSY immediately. https://www.sqlite.org/lockingv3.html Note that the above is true for databases with an old style (non-WAL) journal. I assume similar protections and situations exist in WAL, but can't be certain and they may use a different mechanism. You can figure out whether you have a deadlock or simply the wait timed out by looking at how quickly the error was returned. You can also look at where other threads (or processes if your debugger can attach to multiple processes) are when the error occurs. Are you using explicit transactions? Entity Franework shouldn't cause deadlocks unless you are manually taking control of the transactions. EF can also take a very long time to SaveChanges if you have a large number of entities... > On 14 Jan 2019, at 10:14 pm, Urs Wagner <urs.wag...@man-es.com> wrote: > > We are using entity framework > > The timeout pragma does not work. Is think the timeout is not set, see below > > var esb = new EntityConnectionStringBuilder > { > Metadata = > "res://*/RadaxModel.csdl|res://*/RadaxModel.ssdl|res://*/RadaxModel.msl", > Provider = "System.Data.SQLite.EF6", > ProviderConnectionString = @"data source=" + _dataBase + > ";PRAGMA foreign_keys = ON;PRAGMA locking_mode = EXCLUSIVE;PRAGMA > schema.synchronous = NORMAL; PRAGMA schema.journal_mode = DELETE; PRAGMA > busy_timeout = 100000" > }; > > > -----Original Message----- > From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> On Behalf > Of Hick Gunter > Sent: Monday, January 14, 2019 11:28 AM > To: 'SQLite mailing list' <sqlite-users@mailinglists.sqlite.org> > Subject: Re: [sqlite] [EXTERNAL] SQLite error (5): database is locked > > With journal mode, SQLite supports 1 writer OR n readers; with WAL mode, > SQLite supports 1 writer AND N readers. > > In any case, connections need to indicate if or how long they are willing to > wait for the db file to be unlocked. Default is NO. > > The easiest way is to specify a timeout on the connection. The value needs to > be longer than your longest write transaction is expected to run and shorter > than the latency required by your application. > > -----Ursprüngliche Nachricht----- > Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im > Auftrag von Urs Wagner > Gesendet: Montag, 14. Jänner 2019 10:24 > An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> > Betreff: [EXTERNAL] [sqlite] SQLite error (5): database is locked > > Hallo > > I use several tasks in C# to call Sqlite queries. > No I get the error SQLite error (5): database is locked. > Is it not possible to use more than one tasks with Sqlite? > > Regards > > Urs > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > ___________________________________________ > Gunter Hick | Software Engineer | Scientific Games International GmbH | > Klitschgasse 2-4, A-1130 Vienna | FN 157284 a, HG Wien, DVR: 0430013 | (O) > +43 1 80100 - 0 > > May be privileged. May be confidential. Please delete if not the addressee. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
