In principal, I agree; in practice, that's not the way it's been done in
the Java application server world.
I have two readily available Java database connection pool
implementations available: the one bundled with Apache Tomcat and
Hibernate's c3p0. Neither of these directly support failover. They each
expect the lower level JDBC driver to deal with failover. (This is true
of BEA WebLogic and IBM WebSphere as well, at least as of a few years
ago when I last used them intensely.)
What I'm looking for is very standard stuff in the Java application
server world. The JDBC driver handles failover and/or load balancing to
multiple backend database servers.
- Bruce
On 06/16/2011 07:51 PM, John R Pierce wrote:
> On 06/16/11 1:27 PM, Bruce Adams wrote:
>> Their primary goal appears to be connection pooling. My Java
>> application server (Apache Tomcat) is already pooling database
>> connections
>
> I think JDBC is the wrong layer for this, instead it should be
> implemented in your java connection pool (tomcat, etc), where you
> configure it with the multiple connections and the connection pooling
> rules (master/failover, vs round robin vs whatever).
