I had this problem before. The connection pool is most likely working
properly, the problem must be with your code. One thing that may be
happening is that you are having exceptions or anything that is preventing
you from freeing the connections. Remember that when you are using
resources you *must* use the "finally" statement to make sure your
resources are freed whether or not there was an exception.
At 07:21 AM 3/8/2000 -0500, you wrote:
>Hi,
>I'm having some trouble with my JavaExchange connection pool implementation.
>I'm not sure whether it's a problem with the Javaexchange class, or with my
>code.
>
>The symptoms: the alotted number of DB connections is quickly exhausted.
>
>THe background: I've got a singleton wrapper class for my connection pool,
>which hands out conns.
>All of the methods which use the DB start with connPool.getConn() and have
>the rest of the code enclosed in a try statement. The
>connPool.freeConn(conn) method is called from a finally{} statement.
>
>Quite quickly, the available conns are exhausted.
>Has anyone else had this problem?
>
>Thanks
>Peet
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
