Another solution, less ugly (IMO) than mod_proxy, is removing mod_php by setting up PHP behind mod_fastcgi. In fact, if you remove mod_perl as well by putting your Catalyst apps behind mod_fastcgi, you can have all the threading you desire.
On Fri, Jul 29, 2011 at 8:15 AM, Tomas Doran <bobtf...@bobtfish.net> wrote: > > On 29 Jul 2011, at 12:25, matthew couchman (JIC) wrote: > > Thanks for your reply. Perhaps it was too sweeping a statement but I can >> only say that for my setup mod_perl works fine through Apache alone as does >> php but when I combine them it crashes with memory corruption errors. >> > > (At a guess), don't use the threaded MPM. > > Use prefork and everything will be fine. > > > Cheers > t0m > > > ______________________________**_________________ > List: Catalyst@lists.scsys.co.uk > Listinfo: > http://lists.scsys.co.uk/cgi-**bin/mailman/listinfo/catalyst<http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst> > Searchable archive: http://www.mail-archive.com/** > catalyst@lists.scsys.co.uk/<http://www.mail-archive.com/catalyst@lists.scsys.co.uk/> > Dev site: http://dev.catalyst.perl.org/ >
_______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
