We also experience this with our WebGIS. We never found the cause of this, but some of our customers experience this every day and others never experience it. My research suggests that if you query the MapGuide server with an expired session, some errors occur inside MapGuide and at some point it stops working due to memory leaks or something. Best way to avoid the crashes is to avoid working with expired MapGuide server sessions. So set the IIS session timeout to something lower than the MapGuide timeout or have some keep alive request that triggers both IIS and MapGuide server requests.
-- View this message in context: http://osgeo-org.1560.x6.nabble.com/Additional-monitoring-of-MapGuide-tp5291944p5292249.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users