I noticed this while supporting the NFL Draft, not sure exactly how many 
threads were going through the score code that was causing this exception, but 
the servers were generally processing 200-300 requests per second at the time.  
Yes, connection pooling is turned on for the code in the stack trace reported 
earlier.  This customer was running on an older version of our code, the newer 
version has our own secret sauce of in memory connections.

I will take a look at your unit test and try to write something myself that 
reproduces the problem..  Also, I did modify the Sqlite Wrapper a bit, we 
removed the static locks from SqliteBase.cs as these were causing performance 
issues.. We do a lot with sqlite asynchronously and these locks were a single 
point of contention for everything.  We have been running with these removed 
for over a year now and have had only a few problems.. One was caused by
http://system.data.sqlite.org/index.html/tktview?name=fc994d007d and the other 
was fixed by this check in 
http://system.data.sqlite.org/index.html/info/10d400ebd0 (THANK YOU!).  What is 
the purpose of these locks when Sqlite itself has been compiled as ThreadSafe?



-----Original Message-----
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Joe Mistachkin
Sent: Saturday, April 28, 2012 9:49 PM
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] System.Data.SQLite and pooling problem


Alexander Spence wrote:
>
> I am seeing a similar error since upgrading to 1.0.80.0.  I am still
working on
> trying to reproduce it, but here is a stack trace:
>

Based on your stack traces, it seems you are using the connection pool as
well?  How
many threads are involved?  Is the exception happening consistently or on
intermittently?

--
Joe Mistachkin

_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Please NOTE: This electronic message, including any attachments, may include 
privileged, confidential and/or inside information owned by Demand Media, Inc. 
Any distribution or use of this communication by anyone other than the intended 
recipient(s) is strictly prohibited and may be unlawful.  If you are not the 
intended recipient, please notify the sender by replying to this message and 
then delete it from your system. Thank you.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to