Search This Blog

Wednesday, December 16, 2009

When to use connection pooling

Use WebSphere connection pooling in an application that meets any of the following criteria:
It cannot tolerate the overhead of obtaining and releasing connections whenever a connection is used.
It requires Java Transaction API (JTA) transactions within the Application Server.
It needs to share connections among multiple users within the same transaction.
It needs to take advantage of product features for managing local transactions within the application server.
It does not manage the pooling of its own connections.
It does not manage the specifics of creating a connection, such as the database name, user name, or password

No comments:

Post a Comment