connection-leaks

In my web-application, i make extensive use of a database. I have an abstract servlet, from which all the servlets that need a database connection, inherit. That abstract servlet creates a database connection, calls the abstract method which must be overriden by the inheriting servlets to do their logic, and then closes the connection. I do not use connection pooling, because my application will have a very limited number of users and operations. My question is, what's the worst that can happen if i don't ever close the ResultSet s, PreparedStatement s and Statement s that my inheriting

I am seeing a lot of Connection Resets in Production.There could be multiple causes to it but I wanted to ensure that there are no Connection leakages coming from in code.I am using Jersey Client in code Client this.client = ApacheHttpClient.create(); client.resource("/stores/"+storeId).type(MediaType.APPLICATION_JSON_TYPE).put(ClientResponse.class,indexableStore); Originally I was instantiating client in the following fashion Client this.client = Client.create() and we changed it to ApacheHttpClient.create(). I am not calling close() on the response but I am assuming ApacheHttpClient would do

I'm currently doing some GUI testing on a ASP.net 2.0 application. The RDBMS is SQL Server 2005. The host is Win Server 2003 / IIS 6.0. I do not have the source code of the application because it was programmed by an external company who's not releasing the code. I've noticed that the application performs well when I restart IIS but after some testing, after I have opened and closed my browser for a couple of hours, the application starts to get slower and slower. I was wondering if this behaviour was due to a bad closing connection practice from the programmers : I'm suspecting an open

Tomcat is running a webapp under Windows. After a few days (under very low load), the exception mentioned in the title starts to appear in the logs, no new connections can be established from that point on, the only fix is then to reboot the server. Environment: Latest Tomcat 6 Windows Server 2008 R2 JDK 6 update 30 SQL Server 2008 Kerberos authentication Evidence collected so far: netstat shows no excessive amount of connections ProcessExplorer shows no excessive amount of open file handles system main memory usage is average JVM heap usage is average restarting Tomcat does not solve the