[mapguide-users] ISAPI versus CGI Stability

[Jason Birch]

Makes sense.  I'm guessing that this is why the development list has shown a lot of memory leak hunting.
 
Going to the CGI version would reduce cumulative memory leak problems, but at the expense of forking the cgi on each request (I think that isapi modules typically stay loaded for the life of the IIS service).
 
This is obviously not a long term fix for servers under any real load.
 
Jason

 
________________________________

From: Andy Morsell [mailto:amorsell at spatialgis.com]
Sent: Thu 2006-05-11 9:23 AM
To: users at mapguide.osgeo.org
Subject: [mapguide-users] ISAPI versus CGI Stability



I saw a mention of this on the Mapguide Enterprise beta forum and it helped me, so I thought I would share it.  I do not recall seeing this mentioned in this list or in Project Tracker. 

If you install MapGuide Open Source on Windows for use with IIS, you are instructed to configure the .fcgi extension for the mapagent virtual directory to point to the isapi_fcgi.dll file.  It looks like the ISAPI agent is the component that is having the stability issues I have been fighting with since I installed R1.   After pointing the .fcgi extension to the mapagent.exe file instead, my production server seems to be much more stable.  It has been running under this configuration without a lockup for 4 days whereas it was locking up several times a day previously.

Andy Morsell, P.E. 
Spatial Integrators, Inc. 
http://www.SpatialGIS.com <http://www.SpatialGIS.com>  

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 4740 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapguide_users/attachments/20060511/ea0481e8/attachment.bin