Changes between Version 5 and Version 6 of MGOS21GdalProvider


Ignore:
Timestamp:
Dec 18, 2009, 11:24:17 AM (14 years ago)
Author:
jbirch
Comment:

Clarified the serverconfig.ini options I actually use, and why.

Legend:

Unmodified
Added
Removed
Modified

  • MGOS21GdalProvider

    v5 v6  
    7676== Configuration Parameters ==
    7777
    78 Jason Birch has had more success running a stable GDAL environment in !MapGuide with connection pooling disabled for the GDAL Provider.  In serverconfig.ini, this can be accomplished by disabling connection pooling entirely
     78Jason Birch has had more success running a stable !MapGuide with connection pooling disabled.  In serverconfig.ini, this can be accomplished by disabling connection pooling entirely
    7979{{{
    8080[FeatureServiceProperties]
    8181DataConnectionPoolEnabled = 0
    8282}}}
    83 Or by excluding the GDAL Provider from the connection pooled provider list
     83
     84If you require connection pooling for performance of other providers, you may instead wish to attempt to just exclude the GDAL Provider from the connection pool provider list.  Note that in Jason's experience this improved reliability, but not to the same level as disabling connection pooling entirely; his guess was that the GDAL provider exercises some bug more reliably than the other providers, but the instability may be entirely unrelated.
     85
    8486{{{
    8587[FeatureServiceProperties]
    8688DataConnectionPoolExcludedProviders = OSGeo.Gdal
    87 }}}
     89}}}
     90