Summary: | StatementCache leaks statements/cursors | ||
---|---|---|---|
Product: | Tomcat Modules | Reporter: | Patric Rufflar <patric> |
Component: | jdbc-pool | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All |
Description
Patric Rufflar
2012-12-21 11:31:49 UTC
(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 *** |