Bug 50692 - Improve log message in ThreadPool.logFull
Summary: Improve log message in ThreadPool.logFull
Status: RESOLVED WONTFIX
Alias: None
Product: Tomcat 6
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 6.0.30
Hardware: PC Windows XP
: P2 enhancement with 1 vote (vote)
Target Milestone: default
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 07:42 UTC by Konstantin Kolinko
Modified: 2017-04-07 14:22 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Kolinko 2011-01-31 07:42:52 UTC 
org.apache.tomcat.util.threads.ThreadPool#logFull(..) prints the following message:

Jan 28, 2011 10:43:16 AM org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads (200)
or check the servlet status 

From the message it is not clear, what pool was exhausted. It might be that there are several connectors in the configuration.

It would be better to assign name to the pool (the #setName() method already exists there) and to print that name.

At least it is possible to print a stack trace: that will provide some information.

For reference:
http://markmail.org/thread/ytfqiowlm7vz2jxg
Comment 1 Mark Thomas 2017-04-07 14:22:18 UTC 
This code doe snot exist beyond Tomcat 6.0.x and 6.0.x. has reached EOL.