You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2013/03/22 18:34:11 UTC

[Bug 54337] StatementCache leaks statements/cursors

https://issues.apache.org/bugzilla/show_bug.cgi?id=54337

Konstantin Kolinko <kn...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE
                 OS|                            |All

--- Comment #1 from Konstantin Kolinko <kn...@gmail.com> ---
(In reply to comment #0)
> 1. 
> The AtomicInteger field
> org.apache.tomcat.jdbc.pool.interceptor.StatementCache.cacheSize 
> which seems to be not in sync with the real size of the cache Map.
> (..)

You are wrong:
Map is per-connection. Size is per-pool.

> 2. 
> When the capacity seems (or really is) exceeded, statement.close() will not
> causing to close the wrapped statement causing the cursor to leak.

Yes, it is a bug. Duplicate of 54732.

*** This bug has been marked as a duplicate of bug 54732 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org