Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
The moose likes JDBC and the fly likes Servlet with connection to database Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "Servlet with connection to database" Watch "Servlet with connection to database" New topic

Servlet with connection to database

Thomas Sutton

Joined: Feb 18, 2013
Posts: 1
I have been load testing our code which takes a request from the website performs some checking then updates a db2 database table. We are using a jdbc connection pool and everything is fine until I increased the number of requests to around 3 per second. Then we start to see some strange behaviour. Connections to the db seem to be closed by themselves, connection.close() is not called on the connections that have closed prematurely I'm sure of that. I have checked through the code several times and can't find a reason for this. Does this point to a problem with the jdbc connection pool or the database itself?

Scott Selikoff
Saloon Keeper

Joined: Oct 23, 2005
Posts: 3703

Are you closing the connections yourself? Just because it's in a pool, doesn't mean you shouldn't close every connection in a finally block.

My Blog: Down Home Country Coding with Scott Selikoff
It is sorta covered in the JavaRanch Style Guide.
subject: Servlet with connection to database
Similar Threads
Apache commons dbcp - SocketException: Too many open files
Connection Pooling
I need advice from a guru
Getting connection from pool?
java jdbc and oracle - maximum open cursors exceeded