[Bug 61032] min pool size is not being respected
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 be issued. Instead, it should create connections and add to idle queue if idle queue size is less than minIdle. -- 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
[Bug 61032] min pool size is not being respected
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 total connections (idle+busy) to fall below minIdle connections This causes performance issues and also potential issues by increasing the number of occurrences of having to create the connection when application needs one. I notices this issue and the PR is created in early 2017, more than a year ago. How is everyone working around the issue? -- 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
[Bug 61032] min pool size is not being respected
https://bz.apache.org/bugzilla/show_bug.cgi?id=61032 Jelmer changed: What|Removed |Added URL||https://github.com/apache/t ||omcat/pull/54 -- 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