A long time ago I opened that thread and it seems that we now have found the reason for this application pool crashes!
The crashes starts 2 years ago when when we start publishing MapGuide through a ReversProxy. In the beginning just a few users uses the ReversProxy and that's the reason that the crashes happens quite rarely. But as the number of users increase the crashes arise more often. The only way around was to change the settings of the application pool to be more error-tolerant (allow more errors in a specific time period). As a result the appliation pool stayed alive but with the side-effect that sometimes tooltips and selections doesn't work as expected and the Ajax-Viewer often seems to hang. The reason for the errors were requests send from the ReverseProxy (http://localhost/mapguide/mapagent/mapagent.fcgi) to the webserver (IIS7.5) to keep the connection alive. These request were done as a POST request with no data. And that causes the application pool to crash. Sending a POST request with data (any data - whether it make sense or not) results at least in an error message and leave the application pool staying alive. But without data it just leeds to a crash. I think we can say that this is a security issue, causs someone who knows about this fact can easily terminate the application pool, even without the use of a ReverseProxy. I will create a ticket for this! Gunter -- View this message in context: http://osgeo-org.1560.n6.nabble.com/isapi-MapAgent-dll-crashes-MapGuideAppPool-tp4183774p5022136.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
