You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by "Diethelm Guallar, Gonzalo" <Go...@sonda.com> on 2001/08/08 15:52:03 UTC
Tracing DB connection pool
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?
* 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?
Thanks,
--
Gonzalo A. Diethelm
gonzalo.diethelm@sonda.com
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Tracing DB connection pool
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Diethelm Guallar, Gonzalo" <Go...@sonda.com> 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: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Tracing DB connection pool
Posted by Jason van Zyl <jv...@apache.org>.
On 8/8/01 9:52 AM, "Diethelm Guallar, Gonzalo" <Go...@sonda.com>
wrote:
> 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?
>
> * 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?
Jon has started adding some tests, maybe you could add some more :-)
Though we need to work out the testing harness for a running system using
Cactus/HttpUnit first. I think Kurt was doing some work on that.
> Thanks,
>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org