#17810 [Com]: Instability with IIS/ISAPI

ID: 17810 Comment by: tshazli@linuxmail.org Reported By: fabien.dehopre@itn.skynet.be Status: Open Bug Type: IIS related Operating System: Windows 2000 Server PHP Version: 4.2.1 New Comment: Ok, here is the thing: I have 2 servers load balancing each other. had this problem with one of our servers (PIII dual processor) but not with the other which is a single processor. I tried to format the server, reinstall everything all over again, not apply microsoft patches/fixes...etc. still the problem occurs ONLY on the dual processor server. Then I tried to take one processor out of that box and guess what...IT worked flawlessly. I stress tested it with heavy load test for hours and not once I got the error ever again. I put the processor back to the box and tested it. I got the error again. I tried that many times. Always get the error with dual processor but not even once with single processor. So how to work around the problem? use single processor server. What causes the problem? dont know..It is between PHP and IIS. I am trying to find out the problem by debuging the services but if anyone is interested in reproducing the problem and trying to debug it, use dual processor with win2000 server and IIS5 with any php ver >=4.2.1 and use ADODB or MSSQL connections. Stress test it and you will get the error. Previous Comments: ------------------------------------------------------------------------ [2002-07-27 21:49:37] rasmus@php.net Like it or not, but 90% of the people who contribute to PHP do not use Windows, so it is natural that Windows issues do not receive as much attention. Feel free to contribute Windows-related fixes or go out there and convince some of all these Windows users to help out. ------------------------------------------------------------------------ [2002-07-27 21:38:12] tshazli@linuxmail.org mfischer@php.net; As you know, windows platform servers represent more than 50% of the internet servers. Whether we like it or not, It is a reality. I like PHP and have been working with it for more than 3 years now. I convinced the company I work for and its clients to use PHP instead of J2EE or ASP or Coldfusion and many others. PHP cannot work on a live windows erver with CGI. It uses alot of resources and on heavy load, The server maxs up and dies. ISAPI is the "only" realistic way. If you want PHP to compete and have its presence, Wehether you like it or not, It has to work "fine" on windows platform. That's all what I wanted to say. For you guys who experience this problem, I found a work around to "reduce" the effect of the problem. Pls go to bug #15333 thanks. ------------------------------------------------------------------------ [2002-06-18 04:58:03] mfischer@php.net I advised you to use the CGI version because there hasn't been much development on the ISAPI module and I'm not aware anyone is right now or in the near future working on it. Updated Summary,Category ------------------------------------------------------------------------ [2002-06-18 04:53:58] fabien.dehopre@itn.skynet.be Now when we make a charge test with +/- 4 RPS we get sometime "parse error" and other time we don't get this parse error. We are in ISAPI because the CGI version use a lot of resources. ------------------------------------------------------------------------ [2002-06-18 04:18:42] fabien.dehopre@itn.skynet.be I use ADODB for PHP (http://php.weblogs.com/ADODB). We use a MS SQL database. there is a script that can reproduce the error (it's not sure). <?php require_once("./db/adodb.inc.php"); $db = &ADONewConnection("mssql"); $db->Connect("xxx.xxx.xxx.xxx","user","password","db_name"); $query = "SELECT TOP 10 * FROM table_name"; $rs = $db->Execute($query); while (!$rs->EOF) { $obj = $rs->fetchNextObject(false); print_r($obj); print '<hr>'; } $rs->Close(); $db->Close(); ?> ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/17810 -- Edit this bug report at http://bugs.php.net/?id=17810&edit=1