DBCP has some properties to help with connection pool leaks:
removeAbandoned, logAbandoned. See
http://jakarta.apache.org/commons/dbcp/configuration.html
On 11/10/05, emre akbas <[EMAIL PROTECTED]> wrote:
> Hi,
> I have some general questions about connection pooling and exception
> handling.
> Struts suggests that developers use declarative exception handling. In
> declarative exception handling, there are almost no "try { } catch() {}"
> blocks in the Action classes. Exception occuring in Action classes are
> handled by exception handlers outside the Action classes. Everything seems
> OK so far.
> It is very usual that we open a connection to the database at the beginning
> of the Action class and then close it at the end. When an exception occurs,
> an exception-handler outside of our Action class (in which the exception is
> thrown) handles the exception. Then, what happens to the connection? We
> weren't able to close it, so does it continue to allocate a connection from
> the pool?
> My other question is about the connection pooling itself. Are there any
> tools or ideas to monitor the sanity of the connection pool? Are we somehow
> able to find the classes where leakage occur?
> Thanks in advance.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
