[mapguide-users] RE: Studio Enterprise and Web Studio Cannot Connect Randomly

[Jason Birch]

For anyone who's keeping track...
 
Setting the StartServers to a higher number did not seem to help me.
 
What has seemed to help was setting the StartServers and MaxServers to
the same number.  I guess this is OK if you're not worried about memory
leaks or dynamic resource allocation on your server.
 
It looks to me like any time a MapAgent child process is killed on
Windows, the FastCGI ISAPI handler doesn't get informed about it, and
the first request fails. If you restart IIS after killing a process, you
don't get the error; a new process is just started up.
 
Jason

________________________________

From: Jason Birch [mailto:Jason.Birch at nanaimo.ca] 
Sent: Wednesday, November 15, 2006 12:41
To: users at mapguide.osgeo.org
Cc: Trevor Wekel
Subject: RE: [mapguide-users] RE: Studio Enterprise and Web Studio
Cannot Connect Randomly


Thanks, I'll give that a try.
 
Apparently these can be set on a per-service level, under
 
HKEY_LOCAL_MACHINE\SOFTWARE\FASTCGI\.fcgi
 
And there is an "Environment" setting.  Maybe this could be used to
overcome the problem with the PROJ_LIB variable not getting picked up?
 
http://viewcvs.php.net/viewvc.cgi/fastcgi-isapi/readme.txt?view=markup
 
Jason

________________________________

From: Trevor Wekel
Subject: RE: [mapguide-users] RE: Studio Enterprise and Web Studio
Cannot Connect Randomly


Hi Jason,
 
Telling isapi_fcgi and mod_fastcgi to spin up two servers might help but
I've had trouble forcing them to spin up agents.  mod_fastcgi is
especially obstinate.  Even under load it doesn't like to spin up more
than one agent.  Here are the appropriate settings:
 
For IIS:
 
Increase the registry setting HKEY_LOCAL_MACHINE\SOFTWARE\FASTCGI
StartServers REG_DWORD 1 
 
 
For Apache, modify httpd.conf and increase -minProcesses:
 
Change
 
FastCgiConfig -idle-timeout 120 -minProcesses 1 -maxClassProcesses 4
-multiThreshold 100 -singleThreshold 100 -killInterval 600
 
to
 
FastCgiConfig -idle-timeout 120 -minProcesses 2 -maxClassProcesses 4
-multiThreshold 100 -singleThreshold 100 -killInterval 600
 

Note:  PHP uses a different configuration line and should already be
spinning up 4 processes:
 
FastCgiServer "C:/Program
Files/MapGuideOpenSource/WebServerExtensions/php/php-cgi.exe" -processes
4 -idle-timeout 120 -
initial-env PHP_FCGI_MAX_REQUESTS=500 -initial-env PHP_FCGI_CHILDREN=1^M
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide_users/attachments/20061116/eee5c2bc/attachment.html