Bug 68934 - Log events which exceed Connector parameter limits such as maxConnections
Summary: Log events which exceed Connector parameter limits such as maxConnections
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 10
Classification: Unclassified
Component: Connectors (show other bugs)
Version: unspecified
Hardware: All Linux
: P2 enhancement (vote)
Target Milestone: ------
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-23 01:20 UTC by baron
Modified: 2024-04-23 20:45 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description baron 2024-04-23 01:20:12 UTC
Tomcat 10.1.x 

Tocat allows to set limits on certain Connector parameters, e.g.: maxConnections, maxThreads. It would be useful if logging could be configured to report when these limits were reached.

Logging needn't be super timely, but would be helpful for forensic confirmation that the parameter in question may require tuning.

Ref.: Tomcat Users mailing list thread <https://lists.apache.org/thread/v3s4h1dgg5pgnzwszxmgcgy03zgndrvd>
Comment 1 Remy Maucherat 2024-04-23 14:39:00 UTC
It is not possible to do something generic for everything.

I added a debug log to LimitLatch when going over the limit, which is the structure used for enforcing maxConnections. The latch had some tracing already, but nothing for the actually important event ... This could get verbose if hit all the time though.

maxThreads is about the thread pool, which has a lot of statistics and exceptions when rejecting a task (when maxThreads + queue full). There are multiple possible thread pool implementations so any of them could be doing something slightly different.