Hi, I am not sure whether this message should be in this forum or Tomcat. I have an application where I was using my own ConnectionPool to manage database connections and this has been working really well for us. I have recently re-written this application and decided to use the Tomcat database pooling facility. What I have found so far is that even for very simple queries, the performance has significantly gone down the drain. For example, on one page I had to sit and wait for a few seconds just to load up some prices from the database. I am not sure whether this is directly to do with the use of the tomcat pooling or something else I may have done. Can people please share their experience of using Tomcat 4 DBCP facility. Thanks in advance FK
The secret to creativity is knowing how to hide your sources.
Joined: Jun 29, 2003
An update. I re-wrote the connection class so that it no longer uses the tomcat dbcp and instaed use my old connection pool class and all seems fine on the performance now. Any thoughts? FK
I use Tomcat pooling and have seen no performance problems such as you describe. Interesting... In any case, I think this'd be a better topic for the Tomcat forum so I'm moving this there. Perhaps other Tomcat users will have some insights.
Could this be a versioning issue, I wonder if I should upgrade from my current 4.1.24 to the latest 4.1.30 release and see how it goes. Would it be better to move over to the 5.x stream at this stage and benefit from the newer features of JSP 2.0 and Servlets 2.4. In the meantime if anyone has had any issue please do enlighten me. Thanks. FK