Remy Blank wrote: > Omry Yadan wrote: > >> the problem is that there is NO POOLING for sqlite connections. >> >> >> from sqlite_backend.py : >> >> >> class SQLiteConnection(ConnectionWrapper): >> """Connection wrapper for SQLite.""" >> >> __slots__ = ['_active_cursors'] >> poolable = have_pysqlite and os.name == 'nt' and sqlite_version >= 30301 >> >> >> problem is that my linux is not an 'nt' :), so poolable is false. >> > > This restriction has been introduced in [4493], as it seems to have been > causing crashes. This seems to be due to a bug in pysqlite: > > http://oss.itsystementwicklung.de/trac/pysqlite/ticket/187 > > Unfortunately, there has been no activity on that ticket for 23 months... > > I'd be interested to know if you still get the crash if you enable > pooling on linux. > Enabling pooling seems to have resolved my situation, and I have not seen any crashes yet (in the last 12 hours). Quoting the ticket: "But on Linux, you very quickly run into the following crash (all it takes are 2 concurrent requests to the timeline):"
since my stress test was 15 concurrent connections to the timeline and I had no problems, I assume this is no longer an issue. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
