Win a copy of Java Mock Exams (software) this week in the Programmer Certification (OCPJP) forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Having A DB Connection Which Remains Opened

 
James Gordon
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,

I'm building a web application login module.
Whenever a user login, the application would
access the database SEVERAL times to pick up
information for authentication. An average
of ~60 users would use the system.

I'm a bit worry about the data access portion.
If I would to get and close a database connection
on each login, is it better off if I just keep
a database connection which would be open
whenever the server is up, just to handle
this kind of request? Meaning I don't close it.

Connection pooling might be another way but my
argument is that I only need 1 connection
for that purpose, so pooling doesn't serve
much purpose there.

Please comment.


Thanks in advance.
 
Jeanne Boyarsky
author & internet detective
Sheriff
Posts: 35976
422
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
James,
You could still use a very small connection pool. Even one with one connection. This is better than keeping the connection open because it could go stale.
 
Happiness is not a goal ... it's a by-product of a life well lived - Eleanor Roosevelt. Tiny ad:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!