Connection Pool Standard
Hello all,
I am researching what is the most recommended method of connection pooling in J2EE and maybe someone can help? I have done several searchs here and in google and found many recommendations but no definitive source saying this is the standard. Of course i'm sure some depends on what your app is and so fourth but to summarize I guess here's my questions:
Is it better to use the app servers jndi connection pooling?
Or is it better to use a class to control pooling? and if so which one would be best DBCP, DB Connection Broker, other third party vendors?
All suggestions appreciated thanks
[635 byte] By [
hbskunka] at [2007-10-2 15:18:09]
My recommended method would be to use the connection pooling built into your application server unless there's a reason not to do that.
And yes, the reasons not to do that would be reasons related to your application, which we know nothing about. For example if it is written badly and leaks connections, and you can't correct that problem, you might be forced to find a connection pool that manages that problem more aggressively than the one already in your application server.
DrClap thank you for your response. It is really just a generalized questioned, i have used both in my experience but never really seen a huge difference, I have never personnaly made the decision to implement one or the other for better practices and am curious to what people are using.I had never used jndi in tomcat which is why i would like to clarify a point from the original post that DBCP is what Tomcat uses as it's default pooling when using jndi lookups. There has just been quite a few books that I have read albiet fairly dated that recommend using a class object from someone or designing your own. Now designing your own is not the way to go as there are so many available for any type of app. But I wanted to see what you experts recommend as I am no longer in contact with anyone that does programming.
Thank you very much.
