"Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]> writes:
> One of our apps seems to be leaking DB connections; after some
> hours, new users can't do anything until old users close their
> sessions. Questions:
>
> * Has anybody have similar symptoms? Could this be a leak in
> base Turbine (2.1) code?
It's possible.
> * Is there any way to activate some kind of tracing for the
> connection pool? Something that included stack traces, even
> with all the verbosity associated, so that it was possible
> to track down exactly from where those connections are being
> requested?
You can throw an exception from within the connection pool code, then
immediately catch the exception and log the stack trace. But I don't
know how much information this will buy you...
If you are using the connection pool directly, have you checked all
the places where you get connections to make sure they are returned to
the pool?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
