This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes JDBC and the fly likes Disadvantages of connection pooling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "Disadvantages of connection pooling" Watch "Disadvantages of connection pooling" New topic

Disadvantages of connection pooling

Vinu krish

Joined: Nov 20, 2003
Posts: 16
Hello all,
Can someone tell me the disadvantages of using connection pool? For each connection in the connection pool are some server resources consumed? If so what are the resources.
Thanks in advance,
David O'Meara

Joined: Mar 06, 2001
Posts: 13459

What is your opinion?
One problem is that database resources are 'system' resources and not 'java' resources. This tends to make them heavier, and also causes issues like resource leakage problems. This is true of connections when not using pooling though. A 'problem' with pooling is that you have to pay for all of these resources at the beginning. Opening and closing individual resources is slow, but you only use the resources you need. Pools are required to keep connections ready in case you need them.
Vinu krish

Joined: Nov 20, 2003
Posts: 16
Thanks David. I felt that some resources must be consumed and that is why I posted tht question.
I agree. Here's the link:
subject: Disadvantages of connection pooling
Similar Threads
enterprise application with many users
Using one connection object between multiple threads
Connection Pool and Data Source
Configuring Hibernate to use Tomcat Connection Pool