Configuration differences between the WebSphere Application Server traditional and Liberty: connectionManager element

There are some differences in configuration between connectionManager in Liberty and connection pools in the WebSphere® Application Server traditional.

  • Properties with different names
    • maxConnectionsPerThread, which is maxNumberofMCsAllowableInThread in the WebSphere Application Server traditional.
    • maxIdleTime, which is unusedTimeout in the WebSphere Application Server traditional.
    • maxPoolSize, which is maxConnections in the WebSphere Application Server traditional.
    • minPoolSize, which is minConnections in the WebSphere Application Server 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"/>
    For more information about the accepted time units and formats for the connectionManager element, see Java Database Connectivity 4.1. If you do not specify time units in Liberty, the same default units are used as in the WebSphere Application Server 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 WebSphere Application Server traditional often uses -1 for immediate.
    • Liberty uses a value of -1 to represent never (disabled), whereas the WebSphere Application Server traditional often uses 0 for never (disabled).
    Specifically, this difference applies to the following attributes:
    • agedTimeout
    • connectionTimeout
    • maxIdleTime, which is unusedTimeout in the WebSphere Application Server traditional
    • reapTime
  • Purge policy changes

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

    In the WebSphere Application Server 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 WebSphere Application Server 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 WebSphere Application Server traditional.
    • purgePolicy="ValidateAllConnections", which is equivalent to purgePolicy="FailingConnectionOnly" with defaultPretestOptimizationOverride="true" in the WebSphere Application Server traditional.

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: Monday, 5 December 2016
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rwlp_connpool_diff
File name: rwlp_connpool_diff.html