"Philippe Martinou" <philippe.marti...@sparkom.com> wrote in message news:49887d2f.3000...@sparkom.com... > Hi, > > The first thing to be checked is probably your application. If some method > does not properly close an SQL connection, you will have a leak that will > ultimately lead to this resource exhaustion. > To better trace if this is a case, you may for example create a Wrapper of > SqlConnection that counts connection creation/close.
Thanks for the idea, but isn't that the whole point of the abandoned connections tracking? ie: removeAbandoned="true", removeAbandonedTimeout="20" and logAbandoned="true". I get no logs indicating thta any connections have been abandoned. Does the abandoned tracking work? Additionally, I see this problem in 2 seperate applications I am working on. One uses explicit calls to sql.connection, and the other one uses Hibernate exclusively to do all the transaction handling. Given that I am seeing the problem on both, it leads me to believe that it isn't actually the case of forgetting to close a connection, rather than a connection not being released properly. Thoughts? Thanks, Eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
