Thanks for the attention

No I am not leaking connections - definitely. I don't use a single
connection to the DB in the scenario posted. I just undeploy and deploy the
application via Eclipse.

I do think it may be related to the thread issue - you know better of
course. Tomcat kills the thread and this thread is responsible for cleaning
abandoned connections. Does it make sense ? The threads name is :
[Abandoned connection cleanup thread]

SEVERE: The web application [/ted2012] appears to have started a thread
named [Abandoned connection cleanup thread] but has failed to stop it. This
is very likely to create a memory leak.

@Shultz ; what do yu mean by "While it is possible, your connection pool
should be complaining about that. "

"Have you enabled removeAbandoned and logAbandoned for your
connections" see my first post : remove abandoned is true - I may add log
abandoned


On Mon, Oct 15, 2012 at 10:16 PM, Christopher Schultz <
[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> g rgar,
>
> On 10/14/12 6:00 PM, g. rgar wrote:
> > maybe this is related also :
> > http://bugs.mysql.com/bug.php?id=65909
> >
> > If true then a workaround must be made available
>
> I've looked at this bug and it has nothing to do with connections
> remaining open. That bug is about a thread with the webapp's context
> class loader causing the webapp's ClassLoader to be pinned in memory
> after a webapp stop.
>
> Unfortunately, this mailing list thread has been picked-up as a
> symptom of the threading bug which is entirely untrue.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>
> iEYEARECAAYFAlB8YRUACgkQ9CaO5/Lv0PAGtQCgwI7YNgqVXaLpvYtrX3RrDLoZ
> BogAoI4wQez+y24tb8PdzTjD3n2lZI29
> =kkZt
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to