> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Andi Vajda > Sent: Sunday, March 25, 2007 5:38 PM > > On Sun, 25 Mar 2007, Ofer Nave wrote: > > I'm guessing the PyLucene code starts up and tries to > create threads, > > Nowhere in the Lucene core code is there a "new Thread(" statement. > PyLucene doesn't start any threads either. > > All threads are started by your code or the environment your > run it under. A web framework is likely to start a pool of > threads before PyLucene is even imported. You might need to > customize that thread pooling code to ensure the proper > threading class, PyLucene.PythonThread is used.
That's good to know, as it narrows down the list of possible causes. However, in this case, I am not starting any threads, nor is my web framework starting any threads. I'm running under apache with the prefork module (no threads), under mod_python (may or may not be threaded - don't know enough about mod_python), using the Paste mod_python WSGI wrapper (which according to a dump of the environ arg it passes my WSGI app, is operating under the belief that apache is not multithreaded), which then invokes my code. My code does nothing except import PyLucene and then try to create a Directory() object (both FS and RAM constructors cause the process to freeze). So I can't imagine where a thread is being created if it is not in the PyLucene library itself. I also don't see what I can possibly change to prevent this problem. There is no thread pooling code to customize here. -ofer _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
