> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Andraž Tori > Sent: Sunday, March 25, 2007 1:26 PM > > On Sun, 2007-03-25 at 13:05 -0700, Andi Vajda wrote: > > On Sun, 25 Mar 2007, Andra Tori wrote: > > > > > I am wondering what is the current status of using PyLucene under > > > mod_python ? > > > > As always, when running PyLucene in a threaded environment, > you must > > ensure that all threads are instances of > PyLucene.PythonThread. This > > is so that libgcj's garbage collector is aware of them. > Until libgcj > > lifts the requirements that all threads are registered with it > > *before* they're started > > - which might be the soon the case when the newer gcjs > become sane - > > this is a hard requirement. > > > > does this mean that it will not, under any condition, work > with apache-mpm ?
I'm having the same problem with apache/mod_python. I'm actually using the prefork module, so I should have no problems, but the minute my python app goes into PyLucene code the apache child freezes. You can actually see the effect by looking at the output of 'ps'. I looked up the symbols in the STAT column, and apparently 'S' means sleeping, and an 'l' suffix means multithreaded. When I first start apache, all the httpd processes have 'S' in the stat column. Every time I hit a web page that tries to use PyLucene code, you can see that child's STAT column change from 'S' to 'Sl'. I'm guessing the PyLucene code starts up and tries to create threads, turning the child into a multi-threaded process. Not sure how it ends up freezing, but since I'm not hard-core enough to figure that out, the lesson for me here is I need to rearchitect my app so PyLucene code never has to be in the apache process. :( -ofer _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
