[mod_python] Issues in apache MPM mode

I've been running mod_python under both a threaded and pre-fork version of apache for about 4 months now.  I had a an extremely difficult time getting mod_python and ZSI to work together without getting a segfault.

My suggestion is that if you don't already know how, learn to use the ldd command.  Then run ldd against your "httpd" executable, the "python" executable, all of the apache modules and all of the python modules.  Make sure that there are no requests for the same library from two different directories.

On Solaris 10, you will need to make extensive use of the LDFLAGS="-R/some/lib/dir" in order to keep from getting the "wrong" libraries.  This is because Solaris 10 provides older versions of the libraries that you are likely to want to use in /usr/sfw/lib.  Since many programs also supply their own libraries, the situation is ripe for problems.

Don't bother with development until you are sure you have the library issue under control.


-----Original Message-----
From: mod_python-bounces at modpython.org [mailto:mod_python-bounces at modpython.org] On Behalf Of Jon-Pierre Gentil
Sent: Monday, August 22, 2005 10:03 AM
To: mod_python at modpython.org
Subject: Re: [mod_python] Issues in apache MPM mode

On Monday 22 August 2005 08:30 am, Sébastien Arnaud wrote:

> I wrote it with in mind targeting apache MPM (worker threaded), which
> seemed to me the best mode in apache to lead to high performance.
> Unfortunately, I am discovering that modules are getting reimported
> over and over in this mode, and this is causing apache processes/
> threads to eventually exit with a segmentation fault :(

I'm pretty sure that mod_python only works with the prefork version of 
Apache.


-- 
_________________________________________________________

  Jon-Pierre Gentil               PGP: 0x7E1CBA17
  jabber: jgentil at sebistar.net    web: www.sebistar.net
  "If you think education is expensive, try ignorance."
_________________________________________________________