Hi Justin, On Wed, Dec 3, 2008 at 5:20 PM, Justin Bronn <[EMAIL PROTECTED]> wrote:
> > > WSGIDaemonProcess apache user=apache group=apache processes=5 > > threads=5 > > This could be part of your problem -- it should be `threads=1`. This > is because GEOS is not a thread safe library, and the serialization to > WKT code in particular uses static variables that can cause > unpredictable behavior if multiple threads enter the code at the same > time. Thus, you also made the right choice in choosing a prefork > version of Apache (which Robert should also be using instead of the > worker). i'm well aware of the non-threadsafe-ness - my modwsgi daemon processes run with threads=1, as i did with worker/prefork under the main apache process during testing. > I've been trying to figure this out as well, wish y'all had told me > sooner! There's something fishy going on with Intrepid's version of > Apache. I was able to get mod_wsgi to deploy on both 32 and 64-bit > versions, but I experienced an exception (on 32-bit) and a segfault > (on 64-bit) as a geometry is transformed when trying to view a record > in the admin. I've created a ticket to document this behavior: Did my super-simple case segfault for you (steps: 1. create a GEOSGeometry. 2: call any method on it), or did it only show up via the Django admin? > Try replacing the geos lib of your django with the one from the repo > and let me know if it also works for you. Will give it a go in the morning, thanks a bunch Rob :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. 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 -~----------~----~----~----~------~----~------~--~---
