Opened 10 years ago
Last modified 10 years ago
#880 new defect
Unavailable SQL Server is blocking MapGuide Server
| Reported by: | gBecker | Owned by: | danstoica |
|---|---|---|---|
| Priority: | major | Milestone: | 3.8.0 |
| Component: | SQLServer Spatial | Version: | 3.7.0 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description
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.
A cursory glace at the provider source code reveals that timeout is not supported in the connection capabilities (SupportsTimeout() returns false). As a result, whatever connection is done by any GenericRdbms-based provider will use whatever is the system default for making an ODBC connection.