Connection Pooling Profile Configuration Reference

The connection pooling profile helps you to to view and restrict the number of connections that you create for an end-point. This feature is available for the adapters listed below:

Seapine
ALM
TFS

Note that, this is configured in the common.xml file, and you will be configuring the below listed properties in the common.xml file.

Attribute Name	Type	Description
minEvictionMillis	string	Determines the minimum amount of time an object may sit idle in the pool before it is eligible for eviction. When non-positive, no objects will be evicted from the pool due to idle time alone.
maxWait	string	Specifies the number of milliseconds to wait for a pooled component to become available when the pool is exhausted and the exhaustedAction is set to WHEN_EXHAUSTED_WAIT.
maxIdle	string	Controls the maximum number of ConnectALL core service components that can sit idle in the pool at any time. When set to a negative value, there is no limit to the number of ConnectALL core service components that may be idle at one time.
maxActive	string	Controls the maximum number of ConnectALL core service components that can be borrowed from a session at one time. When set to a negative value, there is no limit to the number of components that may be active at one time. When maxActive is exceeded, the pool is said to be exhausted.
initialisationPolicy	INITIALISE_NONE/ INITIALISE_ONE/ INITIALISE_ALL	Determines how components in a pool should be initialized. The possible values are: INITIALISE_NONE (will not load any components into the pool on startup), INITIALISE_ONE (will load one initial component into the pool on startup), or INITIALISE_ALL (will load all components in the pool on startup).
exhaustedAction	WHEN_EXHAUSTED_GROW/ WHEN_EXHAUSTED_WAIT/ WHEN_EXHAUSTED_FAIL	Specifies the behavior of the ConnectALL core service component pool when the pool is exhausted. Possible values are: "WHEN_EXHAUSTED_FAIL", which will throw a NoSuchElementException, "WHEN_EXHAUSTED_WAIT", which will block by invoking Object.wait(long) until a new or idle object is available, or WHEN_EXHAUSTED_GROW, which will create a new ConnectALL core service instance and return it, essentially making maxActive meaningless. If a positive maxWait value is supplied, it will block for at most that many milliseconds, after which a NoSuchElementException will be thrown. If maxThreadWait is a negative value, it will block indefinitely.
evictionCheckIntervalMillis	string	Specifies the number of milliseconds between runs of the object evictor. When non-positive, no object evictor is executed.