Changes between Version 16 and Version 17 of MapGuideRfc19


Ignore:
Timestamp:
04/19/07 11:42:22 (18 years ago)
Author:
brucedechant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc19

    v16 v17  
    2929Currently, the server only supports FDO providers that support a thread-per-connection or better thread model. Without implementing this RFC there will be no support for single-threaded providers or for limiting the # of concurrent FDO provider connections.
    3030
    31 Note: The existing releases of MapGuide did not check the provider thread model and subsequently allowed single-threaded providers to be used albeit in an unsafe manner.
     31Note: The existing releases of !MapGuide did not check the provider thread model and subsequently allowed single-threaded providers to be used albeit in an unsafe manner.
    3232
    3333== Proposed Solution ==
    3434
    35 The server will be modified to extend on the already existing DataConnectionPoolSize and DataConnectionPoolSizeCustom configuration properties. If the connection pool is disabled or a provider is listed as excluded from connection pooling the above settings will still be used to limit the # of concurrent FDO provider connections.
     35The server will be modified to extend on the already existing "!DataConnectionPoolSize" and "!DataConnectionPoolSizeCustom" configuration properties. If the connection pool is disabled or a provider is listed as excluded from connection pooling the above settings will still be used to limit the # of concurrent FDO provider connections.
    3636
    3737Example settings inside the serverconfig.ini file:
    … …  
    5656
    57571) If the provider thread model is single-threaded then the # of concurrent connections will be limited to 1 regardless of what the above settings have. This is to ensure server stability.
    58 2) The # of concurrent connections specified in the "DataConnectionPoolSizeCustom" property for the specified provider will be used.
    59 3) The # of concurrent connections specified in the "DataConnectionPoolSize" property will be used.
     582) The # of concurrent connections specified in the "!DataConnectionPoolSizeCustom" property for the specified provider will be used.
     593) The # of concurrent connections specified in the "!DataConnectionPoolSize" property will be used.
     60
     61If the server is unable to create a new concurrent connection to a provider that has no more connections available and error will be logged to the server's error log.
    6062
    6163== Implications ==