WAS v8.5 > Reference > Sets

Custom object pool collection

An object pool manages a pool of arbitrary objects and helps applications avoid creating new Java objects repeatedly. Most objects can be created once, used and then reused. An object pool supports the pooling of objects waiting to be reused. These object pools are not meant to be used for pooling Java Database Connectivity connections or JMS connections and sessions. WAS provides specialized mechanisms for dealing with those types of objects. These object pools are intended for pooling application-defined objects or basic Developer Kit types.

To view this dmgr console page, click Resources > Object pool managers > objectpoolmanager_name > Custom object pools.

Use custom object pools to insert additional logic around the following mechanisms:

These features allow for actions such as, clearing the state of an object when returning it to the pool, configuring the state of an object when retrieving it from the pool, or configuring generic pools and sending instructions on how to behave using custom properties.

To use an object pool the product administrator must define an object pool manager using the dmgr console. We can create multiple object pool managers in an Application Server cell.


Pool class name

Specifies the fully qualified class name of the objects stored in the custom object pool.
Information Value
Data type String


Pool implementation class name

Specifies the fully qualified class name of the implementation class for the custom object pool.
Information Value
Data type String


Subtopics


Related


Use object pools


Reference:

Custom object pool settings


+

Search Tips   |   Advanced Search