This topic applies to WebSphere Application Server Liberty V8.5.5.9 and earlier. For the latest Liberty topics, see the WebSphere Application Server Liberty documentation.

Configuration differences between the traditional and Liberty: connectionManager element

There are some differences in configuration between connectionManager in Liberty and connection pools in the traditional.

  • Properties with different names
    • maxConnectionsPerThread, which is maxNumberofMCsAllowableInThread in the traditional.
    • maxIdleTime, which is unusedTimeout in the traditional.
    • maxPoolSize, which is maxConnections in the traditional.
    • minPoolSize, which is minConnections in the traditional.
  • Time duration properties
    You can optionally specify the time duration properties with units in Liberty. For example,
    <connectionManager id="pool1" connectionTimeout="30s" reapTime="3m" maxIdleTime="30m"/>
    See **** MISSING FILE **** for accepted time units and formats for the connectionManager element. If you do not specify time units in Liberty, the same default units are used as in the traditional.
  • Differences between immediate timeout values and never (disable) timeout
    There are differences in the values that represent immediate timeout and never (disabled) timeout.
    • Liberty uses a value of 0 to represent immediate, whereas the traditional often uses -1 for immediate.
    • Liberty uses a value of -1 to represent never (disabled), whereas the traditional often uses 0 for never (disabled).
    Specifically this applies to the following attributes:
    • agedTimeout
    • connectionTimeout
    • maxIdleTime, which is unusedTimeout in the traditional
    • reapTime
  • Purge policy changes

    In Liberty, there are three purge policy values: EntirePool, FailingConnectionOnly, and ValidateAllConnections.

    In the traditional, there are two purge policy values: EntirePool and FailingConnectionOnly, with a second property, defaultPretestOptimizationOverride, determining the behavior of FailingConnectionOnly.

    Purge policies in Liberty, and their traditional equivalents, are as follows:

    • purgePolicy="EntirePool", which is the same for both.
    • purgePolicy="FailingConnectionOnly", which is equivalent to purgePolicy="FailingConnectionOnly" with defaultPretestOptimizationOverride="false" in the traditional.
    • purgePolicy="ValidateAllConnections", which is equivalent to purgePolicy="FailingConnectionOnly" with defaultPretestOptimizationOverride="true" in the traditional.

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: Tuesday, 12 December 2017
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-libcore-mp&topic=rwlp_connpool_diff
File name: rwlp_connpool_diff.html