@gkyle001, back to your original problem (and assuming these upgrades don’t help), I’d think the next step would be for you to confirm for us how iis (in your case, or apache for others) is connecting to Lucee. There are options and it may guide us finding a solution.
1 ) You don’t mention if you’re using the boncode connector for iis. Are you? (Or might you be using the IIS ARR feature z which allows you to do rewrites directly to the Lucee’s internal/tomcat web server?)
(Those using apache would want to see the httpd.conf or any “included” conf files for the lines related to Lucee/tomcat and cfm request processing, as also shown in the Lucee docs.)
The point is that the connection could be made either by AJP or not, and there would be a tomcat “connector” on the receiving end in Lucee’s server.xml–one (at least) for AJP and one for http, each of which itself has tunable settings
Since you have so many sites, it could be that connection slots are exhausted for some requests, thus leading to your error. What to do will depend on your configuration (in the apache end and in the Lucee/tomcat end) as well as any diagnostics you may find per the logs as Zac suggested.
Options include raising the number of threads, decreasing the timeout for unused connections, creating new connectors, and more. Same for boncode configurable settings. There’s no single obvious solution.
- And of course there’s no substitute for diagnostics in a case like this.
First note that boncode has configurable logging, if you’re using that.
And when I first wrote this reply, I thought you were using apache (see my newer reply below). I’d written this next paragraph then. I will leave it for those using apache. I don’t THINK the Tomcat status worker feature works for boncode. Anyone who knows can correct me and I hope to try it later today.
If in using Apache as w web server you find you are indeed using AJP (many do), there’s the option to enable tomcat’s “status worker” feature, which is a monitor of such connections. Besides tomcat’s docs on the feature, I have a blog post with quite a bit more info on the feature, including some challenges and suggestions. Though the post is from 2015, the info still applies. (And while it was focused on cf and iis, indeed elaborating on an Adobe post on the topic, I did indicate how it would benefit Lucee users using apache and AJP just as well.) Finally there’s also potential value for apache users to use Apache’s mod_status feature, as I also point to in my post.
IIS users should consider also using the iis worker process monitor, and its ability to show running requests. That must be enabled in windows server manager (for those on windows server) or “turn on windows features” (for those on windows desktop).
I appreciate these tools may NOT help for your problem. I add them at the end here as just possible additional tools, if the logs or other configuration considerations above don’t help. Or maybe we’ll find someone here gets you to just the right solution.