Hi Chris, and apologies for the seriously belated reply. I post here for the benefit of other users who may be frustrated getting a highly solid Apache to run under a Win environment.
I launched a symfony/Oracle application for customers a couple of days ago, and with PHP 5.1.6, Apache 2.0.59, and eA 0.95, we have had serious stability issues. I've taken the advice on the Apache site and this improved things, but not by much; traffic spikes now bring the service down after ten hours rather than four! The traffic isn't particularly heavy either - we're talking solid use by twenty or so users (so the box has to deal with maybe five concurrent users) over a period of several hours.
Accordingly at present I have configured a schedule to restart the Apache2 service every three hours - not elegant admittedly, but better than having no web app for frustrated users at 4am in the morning! Meanwhile I will take your advice and add FastCGI to the stack. I am determined to get a really reliable Apache/Win environment running, as if we don't it will add fuel to current discussions to port to Win/.net (eek).
Incidentally I haven't found any issues with eA with PHP 5.1.6, and if/when we port to 5.2.1 I shall look forward to getting the latest version. Meantime, thanks for your advice.
Joined: 2007-03-01
Hi Chris, and apologies for the seriously belated reply. I post here for the benefit of other users who may be frustrated getting a highly solid Apache to run under a Win environment.
I launched a symfony/Oracle application for customers a couple of days ago, and with PHP 5.1.6, Apache 2.0.59, and eA 0.95, we have had serious stability issues. I've taken the advice on the Apache site and this improved things, but not by much; traffic spikes now bring the service down after ten hours rather than four! The traffic isn't particularly heavy either - we're talking solid use by twenty or so users (so the box has to deal with maybe five concurrent users) over a period of several hours.
Accordingly at present I have configured a schedule to restart the Apache2 service every three hours - not elegant admittedly, but better than having no web app for frustrated users at 4am in the morning! Meanwhile I will take your advice and add FastCGI to the stack. I am determined to get a really reliable Apache/Win environment running, as if we don't it will add fuel to current discussions to port to Win/.net (eek).
Incidentally I haven't found any issues with eA with PHP 5.1.6, and if/when we port to 5.2.1 I shall look forward to getting the latest version. Meantime, thanks for your advice.