• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Serlvets DB connection pool optimal implementation?

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've created a pool class (DBPool) to create the connection pool (Tomcat). This class is then initialized by the ServletContextListener class.

It might be good to know that my web system got several servlets, each of them containing up to maybe 20 db queries.

My question is, where should I create the connection?
1. In the beginning of each servlet (in the doPost/doGet section).
Then passing on the conn to each method containing the actual db queries.
One connection will then be used for the entire request, no matter then number of db queries performed.
But where should I close the connection?
2. Before each db query.
Then it will be easy to close the connection. But then loads of connections from the pool will be got and closed for each request.
3. Some other implementation
?

Greetings,
Joe

 
reply
    Bookmark Topic Watch Topic
  • New Topic