Studio Enterprise and Web Studio Cannot Connect Randomly

[Trevor Wekel]

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
 

  _____  

From: Chris Gountanis [mailto:cgountanis at mpower-tech.com] 
Sent: Tuesday, November 14, 2006 9:48 AM
To: users at mapguide.osgeo.org
Subject: Studio Enterprise and Web Studio Cannot Connect Randomly


Randomly, I have noticed that Studio Enterprise gives errors like cannot
connect to URL. Web Studio bombs and spits out a whole message box with
page code... basically same error. I have fixed the issue with a reboot
and sometimes a uninstall/reinstall of the extensions. Using IIS/PHP
installation options on XP as my development and testing machine. Why
does this happen?
 
--
Chris

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20061115/fd9e6c87/attachment.html