(Initially sent just to Andi; sending to whole list this time.) OK. I will let you know if I figure anything out.
This is strange to me because from what you're saying, it sounds like mod_python shouldn't work reliably with PyLucene at all. In fact, most of the other things we've tried to do under mod_python worked fine , at least under apache2-mpm-prefork. apache2-mpm-worker seems completely incompatible with PyLucene, probably due to these threading issues. But under prefork, all basic functionality, including some fairly complex querying, works fine. Can you explain to me what it is about my example case that causes PyLucene threading to break where it doesn't elsewhere? Or is it just unpredictable? Thanks! -- jonah On 7/12/05, Andi Vajda <[EMAIL PROTECTED]> wrote: > > Any python thread using PyLucene must be an instance of PyLuceneThread. > This is because the threading support in libgcj insists on > creating and initializing the thread for garbage collection. > > After many months of trying I gave up on trying to tell libgcj about a thread > "after the facts". I could only get it to work on Mac OS X. Hands Boehm, the > author of the libgcj garbage collector, is aware of the issue and intends to > make this work in 'the future'. > > I do not know how what it takes to make sure that the thread under which > you're running PyLucene code is running in a PyLuceneThread under mod_python. > If you manage to make it work (you're not the first one to try), please send > us detailed instructions how to. > > Thanks ! > > Andi.. _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
