Skip Headers

# Internal Connection Pools

Previous

Next

For non-J2EE applications, you typically use internal connection pools. By default, TopLink sessions use internal connection pools.

Using internal connection pools, you can use TopLink Workbench to configure the default (write) and read connection pools (see "Default (Write) and Read Connection Pools") and you can create additional connection pools for object identity (see "Sequence Connection Pools"), or any other purpose (see "Application-Specific Connection Pools").

Using internal connection pools, you can optimize the creation of read connections for applications that read data only to display it and only infrequently modify data (see "Configuring a Nontransactional Read Login").

For information on selecting the type of connection pool to use, see "Configuring External Connection Pooling".

For more information on creating and configuring internal connection pools, see:

- "Internal Connection Pool Creation Overview"

- "Internal Connection Pool Configuration Overview"