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

[Trevor Wekel]

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
 

  _____  

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


Hi Trevor,
 
I've seen this second issue ("There is also an occassional cannot
connect to URL error when a FastCGI Mapagent process has shutdown and
another one has not started up yet") fairly consistently.
 
Is there any way to configure FastCGI to avoid this?  Like a minimum
number of active processes?
 
Jason
 


  _____  

From: Trevor Wekel 
Sent: Wednesday, November 15, 2006 11:04
To: Chris Gountanis; users at mapguide.osgeo.org
Subject: [mapguide-users] RE: Studio Enterprise and Web Studio Cannot
Connect Randomly


Hi Chris,
 
IIS under Windows XP has a hard coded concurrent connection limit - 10
connections I think.  Internet Explorer and the embedded  IE control
within Studio may spin up that many connections to serve a map.  If you
get back a bunch of 403 errors then you are probably hitting this limit.
 
There is also an occassional cannot connect to URL error when a FastCGI
Mapagent process has shutdown and another one has not started up yet.
Typically, this is a single error.  The error "wakes up the agent" and a
second connection attempt should go through successfully.
 
I have also seen rare cases where the Apache/IIS FastCGI link to
Mapagent.exe and php-cgi.exe does not initialize successfully.  This
effectively locks out the Web Extensions.  In these cases stopping
Apache or IIS, manually killing all of the mapagent.exe and php-cgi.exe
process, and restarting Apache or IIS generally corrects the problem.
As an added measure of insurance, stopping and restarting MapGuide
Server can be performed along with the Apache/IIS restart.
 
 
Hopefully this will help,
 
Trevor
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20061115/c1d18962/attachment.html