cific name that is appended as a prefix to the log message. 11.2.11.3 Persistence Services The RDBMS resource pool is a store for all the connections and queries. Queries are called "prepared statements" and "statements" and these will be explained below. A central resource pool conserves system resources and provides more efficient usage of the database connections. Connection pooling is the ability to manage the database connections from a cen- tral pool rather than leaving the connection management to each of the modules. Connection pooling enables product modules or user applications to obtain a con- nection from a pool of connections. This allows load balancing on the connections, rather than overloading a connection while leaving the others free. Once a connec- tion has been created and placed in a pool, product modules or user applications OSS for Telecom Networks can call the getConnection method without performing the complete connection process, thus providing ready access to connections that are already open. Any database operation performed in the product is made via the pool of con- nections. No connection is dedicated to a particular module. User applications which use connection pooling can call the appropriate methods available in the ConnectionPool class to perform specific database operations. The connection pool- ing architecture distributes the connections among the various processes. A "prepared statement" is an object that represents a precompiled SQL statement. An SQL statement is pre-compiled and stored in a PreparedStatement object. This object can be used to execute the statement multiple times. In the transaction and non-transaction modes, prepared statements are applied to all available connec- tions. This ensures that a connection request that is made at any time to perform some database operation has the corresponding prepared statement associated with it. Every prepared statement has a unique ID. Each connection in a connection pool has a vector or tuple whose elements are "wrappers