-----Original Message----- >From: Ferenc Kovacs <tyra3l@xxxxxxxxx> >Sent: Apr 8, 2010 12:53 AM >To: Todd Oberly <taoberly@xxxxxxxxxxxxxx> >Subject: Re: Windows binaries > >On Thu, Apr 8, 2010 at 6:34 AM, Todd Oberly <taoberly@xxxxxxxxxxxxxx> wrote: > >> -----Original Message----- >> >From: Pierre Joye <pierre.php@xxxxxxxxx> >> >Sent: Apr 5, 2010 6:08 AM >> >To: Todd Oberly <taoberly@xxxxxxxxxxxxxx> >> >Cc: php-windows@xxxxxxxxxxxxx >> >Subject: Re: Windows binaries >> > >> >On Mon, Apr 5, 2010 at 6:27 AM, Todd Oberly <taoberly@xxxxxxxxxxxxxx> >> wrote: >> > >> >> I've heard of FastCGI, but never used it before. If I want to get the >> application running ASAP without FastCGI (please don't argue), what would be >> the effect of using the thread-safe VC6 build of 5.2.13? Just a decrease in >> performance? >> > >> >PHP TS is slightly slower than PHP NTS but not in a significant >> >manner. However the stability of the ISAPI may affect your sites much >> >more than the TS vs NTS delta. Many crashes have worst side effects >> >than slowdowns. >> >> A short follow-up. I had the PHP application package running through ISAPI >> for a short time, but then noticed errors like >> >> Faulting application w3wp.exe, version 6.0.3790.3959, faulting module >> unknown, version 0.0.0.0, fault address 0x01b45c80. >> >> in the Event Viewer. Soooo after some investigation, FastCGI is now the >> solution. :) But I then noticed something strange, but am not sure if it's >> related. I then started seeing a warning in my browser when running a >> certain aspect of the script. I'd done this a number of times before, but >> saw no errors. Could there be something about the ISAPI interface that was >> blocking error output? >> >> >http://www.google.hu/search?hl=hu&client=firefox-a&hs=WdP&rls=org.mozilla%3Ahu%3Aofficial&q=InstanceMaxRequests+vs+PHP_FCGI_MAX_REQUESTS&meta=&aq=f&aqi=&aql=&oq=&gs_rfai= >There is a known problem, if you set the PHP_FCGI_MAX_REQUESTS lower than >the InstanceMaxRequests then sometimes the InstanceMaxRequests will be >reached, the fastcgi PM manager will restart the worker, and the visitor >will get a http 500, Internal Server Error. >Others will correct me, if I'm missing something. > >Tyrael I think I've described this poorly, so let me try again. This is how it occurred: 1) I installed the PHP scripts using the vendor-recommended ISAPI method, and verified that it worked completely. The scripts are some glue between a commercial application and IIS for sending mobile phone clients to a web page and allowing users to download them. 2) I then installed and configured the FastCGI system, and upgraded PHP to the recommended 5.2.13 non-thread-safe version. I'm not an expert with IIS, so it took some trial and error to get it working. At no time did I modify any PHP code or change any error logging settings in php.ini. 3) Upon testing this new setup, I started seeing a PHP warning when trying to download a client: "PHP Warning: Missing argument 4..." The warning is legitimate, and I will be reporting it to the vendor (and also fixing it myself, as it looks very simple)...but these errors seem to have started upon installing FastCGI. Unless the difference was moving from PHP 5.2.12 -> 5.2.13 ? I could be wrong. The situation is under control, so this just an inquiry rather than a complaint. Thanks again, Todd -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
