ID: 15722 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: No Feedback Bug Type: IIS related Operating System: Windows.Net Server (RC1) PHP Version: 4.3.0dev New Comment:
Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip Previous Comments: ------------------------------------------------------------------------ [2002-10-21 16:36:16] [EMAIL PROTECTED] Yes, I tried. No help, problem still occurs. Appears to be something related to shutting down a worker process that has the PHP ISAPI loaded.... ------------------------------------------------------------------------ [2002-10-19 17:10:32] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-02-25 21:12:41] [EMAIL PROTECTED] I've been running the latest PHP4.2.0-dev build running as a ISAPI filter and ISAPI script engine in IIS 6 and noticed that after I run server side PHP code the follow warning will be logged to the System event log: - - - - - - - - - - - - Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 1013 Description: A process serving application pool 'DefaultAppPool' took too long to shut down. The process id was '3472'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. - - - - - - - - - - - - IIS 6 has many new features including the concept of application pools and worker processes. This event log error indicated that a web site in the DefaultAppPool had a process that took longer then 90 seconds to shutdown so was subquently terminated. The web site running in this pool only runs PHP code so I was curious why the ISAPI version of PHP process isn't shutting down properly after being executed. Switching to the CGI version of PHP will make this event log entry stop appearing. Can you guys check on this and let me know if this is the intended behavior of ISAPI PHP? There's probably some minor changes need to make the ISAPI version of PHP 100% compatible with IIS 6... ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=15722&edit=1
