https://issues.apache.org/bugzilla/show_bug.cgi?id=54217
Levan <informatik0...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |
Resolution|FIXED |WONTFIX
--- Comment #10 from Levan <informatik0...@gmail.com> ---
Hi.
It seems like the issue initially described in this bug report is still present
for the currently latest Tomcat version 7.0.50. Although now Tomcat sometimes
manages to close additional connections after reloading, sometimes the number
of connections are increased after one reload and then kept steady.
But I still could reproduce the initially described issue (although again not
that easy: it may be related to the frequency of successive reloads). Seems
like it's just a matter of time, i.e. if Tomcat has enough time after reload,
it manages the connection pool more or less as it should. As Mark mentioned in
the "Comment 9" the closeMethod "speeds up the freeing of resources that would
otherwise be freed by GC.", and it looks like the speed is the defining factor.
When using the solution presented by Konstantin Kolinko (to use
closeMethod="close") all WORKS just fine, and the number of connections
reserved are kept STRICTLY as defined in the context.xml file. So it appears
that using closeMethod="close" is the ONLY true way (at the moment) to avoid
"PSQLException: FATAL: sorry, too many clients already" exception.
I'll update my post at Stack Overflow
(http://stackoverflow.com/questions/13595794/jdbc-connection-pool-runs-out-of-connections-when-context-reload-true-is-enabl)
to reflect this situation.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
