Windows-server-php+iis6.0+mysql+windows Server 2003 always causes app address pool to stop running?

First describe the major premise:

The server is configured with Windows Server 2003 + IIS6 + MySQL + php[isapi mode, and there are 13 virtual sites on the site, of which 4 sites are pure PHP scripting sites, others are ASP or ASP. NET sites, so the server does not is so pure.

Now the question is,

Of these 4 PHP sites, one is the Community system built by dzx!2.5 (a), one is a microblog platform (B) built using Jishigou, one is the User Center (C) built using Ucenter, and the last one is written by itself (D).

Above a, B, C, D to create a site, the application of their own program address pool corresponding to: a1,b1,c1,d1;

In the case of large changes in traffic and IP, site A's A1 application address pool is always fake animation, but other sites B, C, D can be normal access, need to manually reclaim and release the current A1, and even can not start the World Wide WEB Publishing Service services normally. Log on to the server to see, always pop up this hint (for example):

All of the above error messages are running in PHP + IIS + ISAPI mode;

If you change PHP's operating mode to fastcgi, this will not happen, but the number of threads in fastcgi always prompt full, so you need to open a larger thread to resolve.

Finally, site A uses the dzx!2.5 as the native system, the front-end is not modified, modified for the background.

Reply content:

First describe the major premise:

The server is configured with Windows Server 2003 + IIS6 + MySQL + php[isapi mode, and there are 13 virtual sites on the site, of which 4 sites are pure PHP scripting sites, others are ASP or ASP. NET sites, so the server does not is so pure.

Now the question is,

Of these 4 PHP sites, one is the Community system built by dzx!2.5 (a), one is a microblog platform (B) built using Jishigou, one is the User Center (C) built using Ucenter, and the last one is written by itself (D).

Above a, B, C, D to create a site, the application of their own program address pool corresponding to: a1,b1,c1,d1;

In the case of large changes in traffic and IP, site A's A1 application address pool is always fake animation, but other sites B, C, D can be normal access, need to manually reclaim and release the current A1, and even can not start the World Wide WEB Publishing Service services normally. Log on to the server to see, always pop up this hint (for example):

All of the above error messages are running in PHP + IIS + ISAPI mode;

If you change PHP's operating mode to fastcgi, this will not happen, but the number of threads in fastcgi always prompt full, so you need to open a larger thread to resolve.

Finally, site A uses the dzx!2.5 as the native system, the front-end is not modified, modified for the background.

It is not recommended to use the ISAPI method, Http://www.iis.net/download/FastCGI

C:\WINDOWS\system32\inetsrv\fcgiext.ini content for reference only

[Types]php=PHP[PHP]ExePath=D:\php\php-cgi.exeInstanceMaxRequests=10000EnvironmentVars=PHP_FCGI_MAX_REQUESTS:10000

Several key points in php.ini are for reference only

output_buffering = Oncgi.force_redirect = 0cgi.fix_pathinfo = 1fastcgi.impersonate = 1

Security considerations in the PHP.ini

disable_functions = system,passthru,shell_exec,exec,popen,proc_openenable_dl = Off

Try to set up a separate temp directory in php.ini, etc.

upload_tmp_dir = "d:/tmp/uploadtemp/"session.save_path = "d:/tmp/sessiondata/"date.timezone = "Etc/GMT-8" ; GMT+8mbstring.language = Neutral ; Set default language to Neutral(UTF-8) (default)mbstring.internal_encoding = UTF-8 ; Set internal encoding to UTF-8

It is recommended that you use thread-safe PHP on the Windows platform and recommend that all PHP sites use the same program application pool.

If possible, don't run PHP on the Windows platform.

