hi, Sometimes one of our production Tomcats will start with the maximum (200) number of threads in the https pool. That is, it doesn't start with some minimum and works its way up to the maximum, it immediately starts with the maximum. There's no reason for it since most of the threads stay idle through the lifetime of the Tomcat. The issue is that this takes up memory and eventually something pushes the Tomcat over the edge and it dies with an out of memory error. Any ideas on how to debug or solve this?
The Tomcat version is 9.0.64.0, running on Amazon Linux 2 (amd64) and Java Corretto 1.8.0_312-b07. Thanks, Jon.
