On 31. aug. 2005, at 19.02, N. C. Deepak Ramesh wrote: Hi, Hi, I, I'm sorry to say, gave up on PyLucene.PythonThread. Basically, the only thing I did (with cherrypy 2.1(svn 525)) was to pass a custom serverClass to cherrypy.server.start() (The WorkerThread in my derived _cherrypywsgiserver inherits from PyLucene.PythonThread in stead of threading.Thread). On Linux this sort of works, sometimes...but never for long. Un-scientifically speaking - most times when I start the server I get "GC Warning: Out of Memory! Returning NIL!", but sometimes the server starts without errors. When the server is started it will report "socket.error: (11, 'Resource temporarily unavailable')" on any attempt of executing a PyLucene enabled method. The funny thing is that the exact same code works 100% on Mac OS X (10.4.2). Unfortunately for me my servers are running Linux. regards /rune "In any project that is multi-threaded, most bugs will come from threading issues. This is regardless of programming language -- it's a deep, as yet ununderstood property of threads." -- Guido van Rossum |
_______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
