Jerry Asher wrote: > Whenever I think about php + aolserver, I am struck by what I've seen in > the past. Comments at the php sites that php + aolserver isn't stable or > ready for production. > > Am I confused about this? > > Also, do php programs embedded within aolserver benefit from: > > A) aolserver's db connection pooling? > B) aolserver's multithreaded model? > C) ??? > > Due to the stability issues, I haven't seen much value in adding php to > aolserver, and not just letting apache and aolserver run side by side with > apache hosting php. > > ??? > > Thanks, > > Jerry
It works fine almost all the time. I originally had this setup because we were using the same server (we only had one!) to try out openacs and to serve webmail, for which we were using SquirrelMail (written in PHP). Sometimes threads would hang -- it seemed that if users had inboxes with too many (i.e. thousands) of messages, php would time out, as its designed to do, but the aolserver thread wouldn't die, and enough hung threads would hang (but not crash) aolserver. It was nothing too terrible, so we just set a cron job to periodically restart the server to clear all the threads out before they got to that critical level. When we upgraded to RedHat 6.2 to 7.2, something in the webmail script that displayed the contents of the inbox consistently crashed aolserver. I've never been able to track it down, nor have I seen the problem with anything else. You can look at the bug (http://bugs.php.net/bug.php?id=14365) if you are interested. Now we have more servers so we use apache for webmail and aolserver for everything else (though no PHP except for webmail). So I wouldn't recommend it, and there certainly isn't any benefit, but if you have to use it, it will probably work. Unless it's SquirrelMail on a RedHat 7.* box -- that definitely will not work! -- Sean Redmond BMA Information Systems
