Re: Connection Pooling
kuassi.mensah@gmail.com wrote:
On May 25, 1:49 pm, Arne VajhHj <a...@vajhoej.dk> wrote:
Chase Preuninger wrote:
What is the best way to create/get a database pool for a serious web
application?
Use the database connection pool capability in the app server.
Tomcat, JBoss, WebSphere, WebLogic etc. all supports it.
The problem with middle-tier connection pools is that they cannot span
JVMs or midlet0er instances.
That is not a problem. It is an advantage. Because interacting with pool
is then a local call.
Oracle's Database Resident Connecton Pool
http://www.oracle.com/technology/tech/php/pdf/php-scalability-ha-twp.pdf
solves this problem; unfortunately it is not (yet) exposed to Java
only PHP and Ruby/Rails (primarily because these are process based not
thread based).
That solution is used not because it is a better solution, but
because the traditional Java/.NET/C++ solution does not work with PHP.
You can use DRCP from Java.
http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-caching-pooling.html
describes how to specify the JDBC connection URL.
I think the interest from Java will be low. A local pool is faster. The
only benefit of a central pool is if the workload tend to be uneven
distributed among app servers - in that case a central pool will
use less resources.
Arne