No. I disabled the offending modules all of which use sqlite3, but it means my webapp is running in a degraded mode. I am waiting for someone else to have this problem and solve it since I am not so knowledgeable.
I did solve the sqlite3 problem by isolating the connection using: self.local=threading.local() however every once in a while a new thread is created that doesn't know about the existing connection object, and the webapp crashes despite having fixed the problem. But even in the degraded mode, my webapp periodically (maybe every few days) resets all its values and creates a new thread (or process, I am in the dark what is happening). This seems to happen in WSGI but not in the interactive mode. One explanation I have cooked up is that Python 3.2.3 runs in its own internal multithreaded mode that mod_wsgi has no control over, and that is the new default we need to deal with. On the other hand, it could be a Python bug. My server box which is running older software runs the same webapp with no problem. -- Gnarlie On Tuesday, November 6, 2012 2:24:01 PM UTC-7, Graham Dumpleton wrote: > > Did you ever sort out why this was happening? > > Graham > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To view this discussion on the web visit https://groups.google.com/d/msg/modwsgi/-/UuxUk0DU7poJ. 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/modwsgi?hl=en.
