ID: 27081 Updated by: [EMAIL PROTECTED] Reported By: ryan at rbftpnetworks dot com -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Windows Based O/S Running IIS PHP Version: Irrelevant New Comment:
This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. "If you experience 100% CPU usage after some time, turn off the IIS setting Cache ISAPI Application." Previous Comments: ------------------------------------------------------------------------ [2004-01-29 04:34:52] ryan at rbftpnetworks dot com Description: ------------ Every now and again, approx 1hr-36hrs, the machine will explode to FULL CPU and I would get the error message below in the Server Logs. The CPU power would be taken up by the dll that runs the IIS PHP Isapi in protected web mode. I would either have to restart IIS (if I can gain terminal access) or restart the server. Upon searching the internet for other people with the same problem, I found many people - that still have not found a resolution to this problem. I feel that my case is slightly different. ERROR MESSAGE: The HTTP server encountered an unhandled exception while processing the ISAPI Application ' php4ts!php_execute_script + 0x21F + 0x8B9B1B41 '. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp. -- A Fix Below: I seem to have found a Fix for the 100% CPU bug when running PHP under ISAPI mode under IIS. You need to make sure that "Cache ISAPI Application" is unticked on all sites that you are running the PHP module on. This seems to work fix the problem. System memory is used more greatly, but the CPU never locks up at 100%. This fix has been tested on high traffic sites using PHP ISAPI over a period of 2 weeks, and seems fine. Please reply if the fix does/does not work for yourself. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=27081&edit=1
