Github user sakalaramesh commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/54#discussion_r216162039
--- Diff:
modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java
---
@@ -622,6 +622,11 @@ protected void release(PooledConnecti
https://bz.apache.org/bugzilla/show_bug.cgi?id=61032
--- Comment #2 from sakala.ram...@gmail.com ---
PoolCleaner is closing connections when idle connection count is more than
minIdle. It should not do that as pool is expected to always have more than
minIdle connections in the idle queue ready to
https://bz.apache.org/bugzilla/show_bug.cgi?id=61032
--- Comment #1 from sakala.ram...@gmail.com ---
I am also running into this issue. My understanding of minIdle is the number of
connections readily available in the pool at all times to avoid creating
on-demand. We are seeing the number of of to
Am 05.09.2018 um 00:32 schrieb Mark Thomas:
The proposed Apache Tomcat 9.0.12 release is now available for voting.
The major changes compared to the 9.0.11 release are:
- Fix multiple issues associated with using the asynchronous Servlet
API in combination with HTTP/2
- Add recursion to
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
11 matches
Mail list logo
