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. Thanks
[This message has been edited by Rishi Kant (edited August 02, 2001).] [This message has been edited by Rishi Kant (edited August 02, 2001).]
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads