Jeff Watkins wrote:
Is it possible that the reloader thread has been the cause of the
Database Locked errors? If the reloader is causing two VisitFilter
instances to be created and BOTH are trying to create the DB, that
would certainly be a problem.
I've been wondering if perhaps the table creation and table population
queries are getting called from different threads/connections somehow.
Catwalk has the same problem on PostgreSQL (you have to create the
tables by hand) and looking at the logs, it seems the create table query
never completes even though it's a valid query (perhaps it never
commits?). The end result is that 'ps ux' reports "Idle in transaction"
and the create table query sits, holding up everything else. I don't
really understand how the hub mechanism works (I'm under the [possibly
mistaken?] impression it creates a pool of connections and that
different threads may get different connections). I'll see if I can't
trace the Catwalk code as I'm guessing your issue and the Catwalk issue
are related.
Cliff
