free pool

If the number of connections equals Minimum connections, the connection will not be closed and will remain in the free pool.

The thread then checks to see how many connections are in the free pool, and compares this to the value of the Minimum connections property.

Each bean class can define the size of its own free pool using this element.

When a block of memory is returned to the free pool, the bucket index is calculated just like it is done with allocation.

As the free pool for this factory is empty, the Connection Manager creates a new connection, c1, and returns it to the application.

In this situation, the Connection Manager will take the connection and put it back into the free pool.

The allocator then looks for an object in the free pool before calling malloc.

Freed memory that is not released to the operating system is restored to the free pool and is available for allocation again.

Instead of calling free, your delete operator adds the freed object to a list called the free pool.

Are you sure you want to move the selected media to the free pool?

Although you can map the pool size extensions, the application servers treat the free pool differently

Move to Free Pool failed

Unused timeout: How long a connection will remain in the free pool before it is closed