Hi all,
on a side note I can confirm that the same problem also happens with OGR Provider (we're using it to connect to PostgreSQL). If a map is accessed with a layer that uses a non reachable PostgreSQL (f.i. a development instance), server stops responding for a lot of time also to other requests that belong to maps that do not reference the problematic database. It seems that MapGuide on the whole is waiting for timeout to expire before serving other requests. For a quick solution the only way is to restart MapGuide, which is obviously problematic as expires live sessions. I have not played with customized timeout but IMHO it seems a bug. Regards, Gabriele Monfardini
_______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
