[Fdo-trac] [fdo-trac] #880: Unavailable SQL Server is blocking MapGuide Server

[FDO]

#880: Unavailable SQL Server is blocking MapGuide Server
---------------------------------+------------------------------------------
   Reporter:  gBecker            |       Owner:  danstoica
       Type:  defect             |      Status:  new      
   Priority:  major              |   Milestone:  3.8.0    
  Component:  SQLServer Spatial  |     Version:  3.7.0    
   Severity:  3                  |    Keywords:           
External_id:                     |  
---------------------------------+------------------------------------------
 We are currently using MGOS 2.4 (FDO 3.7) and we faced some problems with
 a temporarily unavailable SQL Server.
 Every time the SQL Server becomes unavailable the MapGuide Server doesn't
 respond anymore and all other requests
 that were send to the MapGuide Server, regardless of whether they are
 referencing the unavailable SQL Server or not, were blocked.

 The MapGuide Server doesn't respond not until the MapGuide Server/FDO
 reachs a timeout (1-2 minutes).
 On a production environment the MapGuide Server seems to never become
 available again.

 I would expect a behavior similar to the other providers like the SHP or
 SDF Provider where the broken connection is recognized immediately and an
 error is logged.

 Another user has noticed the same behaviour for the OGR Provider.

 When testing FDO 3.8 through the FDO Toolbox then this error still occurs.
 The timeout period then seems to be around 20sec. but this is still to
 long.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/880>
FDO <http://fdo.osgeo.org/>
Feature Data Objects