Sounds like you don't need a connection pool.
Up vote 1 down vote favorite share g+ share fb share tw.
For example, I may open a static connection and use it for multiple sql query, then finally when the program finish, I close the connection. Most of the program I am dealing with, are not multi-threaded, so I don't see the benefit of using connection pool in such situation. Would anyone can answer my question, thank you.
Thanks in advance. Java jdbc link|improve this question edited Feb 16 '11 at 1:59corsiKa24.4k42353 asked Feb 16 '11 at 1:58gunbuster363670115 64% accept rate.
You might consider using a connection pool that offers you better connectivity i.e. Will wait for the DB server to recover from a restart and then connect again. Connection pools also ping the database server regularly to check if everything is alright, perform other connectivity tests, retry connections, log useful information and more.
– Pantelis Sopasakis Feb 17 '11 at 17:47.
For example, I may open a static connection and use it for multiple sql query, then finally when the program finish, I close the connection. Most of the program I am dealing with, are not multi-threaded Sounds like you don't need a connection pool.
You don't ever need a connection pool. It can be useful if you require enforcement on having a limit number of connections.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.