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

[FDO]

#880: Unavailable SQL Server is blocking MapGuide Server
-------------------------------+---------------------
 Reporter:  gBecker            |        Owner:  jng
     Type:  defect             |       Status:  new
 Priority:  major              |    Milestone:
Component:  SQLServer Spatial  |      Version:  3.7.0
 Severity:  3                  |   Resolution:
 Keywords:                     |  External ID:
-------------------------------+---------------------
Changes (by jng):

 * milestone:  3.8.0 =>
 * owner:  danstoica => jng

Comment:

 DeepSeek analysis: This is a two-pronged issue:

 1. The FDO provider does not support connection/command timeouts
 2. The MapGuide connection manager is holding a global mutex when trying
 to open a FDO connection. If such a connection is opening, it is
 essentially "holding up" all the other thread requests to an any FDO
 connection until the open operation completes or fails. So those other
 threads are blocked, giving the impression of an unresponsive MapGuide
 Server.

 Addressing 1 does not address 2. Addressing 2 requires more analysis to
 determine if we can do more fine-grained locking so that other FDO
 connection open requests are not being held up.

 Either way, deleting milestone and revisiting after FDO 4.2 / MGOS 4.0
 milestones.
-- 
Ticket URL: <https://trac.osgeo.org/fdo/ticket/880#comment:2>
FDO <http://fdo.osgeo.org/>
Feature Data Objects