Home/ Questions/Q 4572710
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T19:41:03+00:00

I’m building a Java based web app (primarily JSPs deployed with Tomcat). The number

  • 0

I’m building a Java based web app (primarily JSPs deployed with Tomcat). The number of users will never be more than ~30 people. It is a work log, so the users will constantly be updating/accessing the database (SQL Server). There are many methods in the web app that require a connection to the database.

I open a new connection each time one is required (I also close it appropriately), but this seems like a lot of opening/closing of connections. Does connection pooling apply to this situation? I’m trying to understand the role of the pool, but I’m confused; would there be a connection pool for each user?

If I’m way off track (which I have a suspicion I am), then is there a better solution to this problem? Is there even a problem?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You certainly could pool connections to the database. Generally you’d use one pool per DB (though there could be reasons that you’d have more).

    You’re right to ask whether there’s even a problem. Connection pooling is going to reduce the number of new connections that have to be negotiated, so it will reduce the time it takes to service a request and also reduce load on the servers. Also it will reduce the number of sockets used, which (for larger applications) can be a factor in system performance.

    However: do you have a performance problem that you’re trying to solve? Are response times acceptable? Is load acceptable? Balance what you’d gain in perf versus development cost. Pre-built connection pools exist, so it’s likely easy to integrate one. But it’s not free and optimization should generally be done with specific goals, not “because I should”.

    • 0