Re: [mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

Hi, I've created a new ticket: #880 http://trac.osgeo.org/fdo/ticket/880 Gunter -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Unavailable-SQL-Server-hangs-up-MapGuide-Server-tp5102207p5102843.html Sent from the MapGuide Users mailing list archive at Nabble.com.

Re: [mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

All MapGuide can do is open an FDO connection and set an optional timeout beforehand. Any knowledge about an unreachable server is inherently FDO provider-specific, and should be handled by the FDO provider itself. The burden should be the FDO provider to bail immediately if it finds that its

[mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

Hi, we are currently using MGOS 2.4 and our customer faced some problems with a temporarily unavailable SQL Server. Every time the SQL Server becomes unavailable the MapGuide Server doesn't respond anymore after a short time. It seems that the subsequent requests from users to that broken

Re: [mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

There was a serverconfig.ini configuration property introduced some time back to apply connection timeouts for certain FDO providers. http://trac.osgeo.org/mapguide/ticket/1793 Whether the SQL Server FDO provider will respect whatever timeout you pass to it. You should ask the FDO mailing list

Re: [mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

Hi Jackie, it seems this only belongs to the WMS Provider and I really don't think that this is the root problem. So, I started further investigation and created two maps in Maestro with some layers that references a SHP FeatureSource. In the second map I added also a layer that references a

Re: [mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

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

Re: [mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

I think this is an FDO provider problem then. It should be checking for the un-reachable server condition (if that's even possible) and bail immediately instead of waiting for the timeout to elapse. - Jackie -- View this message in context:

Re: [mapguide-users] Unavailable SQL Server hangs-up MapGuide Server

Yes, I agree. But could it be that there is also a problem in MapGuide? It seems that this scenario blocks all the other FDO providers. One FDO provider shouldn't affect the others. Isn't this handled by MapGuide itself? Gunter -- View this message in context: