ArcSDE, FastCGI+IIS

[Paul Ramsey]

I am pretty sure FastCGI + Apache is the more-tested combination, so  
probably more stable.
Growing processes is Bad News (tm).  Mapserv.exe shouldn't be leaking  
but perhaps it is.  As a stopgap, set your fcgi workers to shut down  
after 50 or 100 accesses.  That way they shut down cleanly sooner  
rather than nastily later.  You'll spawn workers slightly more often,  
but the penalty isn't too bad amortized over a few hundred requests.

On 20-Dec-06, at 3:29 PM, Mike Saunt wrote:

> Hi All
>
> Wondering about the users out there who have had experience with  
> ArcSDE + FastCGI with IIS or with Apache
>
> We got it all going today which we were very happy about!
>
> I'm wondering if anyone has experience with the setting up of the  
> FASTCGI / IIS - we got there eventually (and we'll document and  
> post our experiences) but we're now wondering whether the  
> combination of the three will be the best or whether we should move  
> ArcSDE / FastCGI / MapServer CGI across onto Apache - still running  
> on Windows.  Bascially FastCGI processes seem to bomb out every now  
> and then (says SDE client memory errors, network errors) and I'm  
> wondering whether the FastCGI on IIS is the most stable.  When  
> looking at the mapserv.exe processes in the Task Manager they  
> increase in memory until they drop out.
>
> There seems to have been alot more experiences of FastCGI on Apache...
>
> Any thoughts / insights appreciated.
>
> Cheers
> Mike
>
>
>
>