Forums Register Login

Disadvantages of connection pooling

+Pie Number of slices to send: Send
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,
Vinu
+Pie Number of slices to send: Send
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.
+Pie Number of slices to send: Send
Thanks David. I felt that some resources must be consumed and that is why I posted tht question.
Hey, I'm supposed to be the guide! Wait up! No fair! You have the tiny ad!
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 7128 times.
Similar Threads
Connection Pool and Data Source
Using one connection object between multiple threads
JSP
Configuring Hibernate to use Tomcat Connection Pool
enterprise application with many users
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 11:40:11.