jQuery in Action, 3rd edition
The moose likes JDBC and Relational Databases and the fly likes Using DriverManager versus Connection Pooling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "Using DriverManager versus Connection Pooling" Watch "Using DriverManager versus Connection Pooling" New topic

Using DriverManager versus Connection Pooling

Rishi Kant

Joined: Apr 18, 2000
Posts: 18
Lot has been said about the advantages of using Connection Pooling in JDBC 2.0.
In our application, we have tried both options..using datasource and connection pooling and using DriverManger.getConnection().We have found that the second option ie DriverManager.getConnection() is faster and more reliable.When using datasource.getConnection() we had frequently encountered ConnectionWaitTimeout exception..also the application sometimes becomes very slow.We are using Oracle 8.x for database.Since ours is a large organization,changing the adminstrator options for the datasource,like increasing the size of connections in a pool, would be the last option to be considered.
We are using Websphere as our application server.
Also we are not using EJBs,we are using jsp and beans for database access.
Any thoughts/comments from the members of this forum would be very helpful.

[This message has been edited by Rishi Kant (edited August 02, 2001).]
[This message has been edited by Rishi Kant (edited August 02, 2001).]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Using DriverManager versus Connection Pooling
It's not a secret anymore!