marcsaeg 01/04/22 19:16:03
Modified: src/share/org/apache/tomcat/util Tag: tomcat_32
ThreadPool.java
Log:
Added a log message to indicate that the thread pool has been
exhausted. The log message will only show up in log levels of
INFORMATION and higher.
Exhuasting the pool is not an error condition, but if it happens
often enough it probably indicates that the server configuration
needs to be changed.
Revision Changes Path
No revision
No revision
1.9.2.2 +6 -3
jakarta-tomcat/src/share/org/apache/tomcat/util/Attic/ThreadPool.java
Index: ThreadPool.java
===================================================================
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/Attic/ThreadPool.java,v
retrieving revision 1.9.2.1
retrieving revision 1.9.2.2
diff -u -r1.9.2.1 -r1.9.2.2
--- ThreadPool.java 2000/07/06 22:20:17 1.9.2.1
+++ ThreadPool.java 2001/04/23 02:16:03 1.9.2.2
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/Attic/ThreadPool.java,v
1.9.2.1 2000/07/06 22:20:17 alex Exp $
- * $Revision: 1.9.2.1 $
- * $Date: 2000/07/06 22:20:17 $
+ * $Header:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/Attic/ThreadPool.java,v
1.9.2.2 2001/04/23 02:16:03 marcsaeg Exp $
+ * $Revision: 1.9.2.2 $
+ * $Date: 2001/04/23 02:16:03 $
*
* ====================================================================
*
@@ -205,6 +205,9 @@
int toOpen = currentThreadCount + minSpareThreads;
openThreads(toOpen);
} else {
+ // XXX There really should be a way to log which pool is
exhuasted
+ loghelper.log("Pool exhausted with " + currentThreadCount + "
threads.");
+
// Wait for a thread to become idel.
while(currentThreadsBusy == currentThreadCount) {
try {
