Hi there,
I am trying to deploy our production service on the Tomcat 3.3 platform
(Solaris8, JDK 1.3.1) but am very often facing the instability problems.
Somehow, the ThreadPool just runs out of steam and blocks Connectors from
receiving any more requests.
Looking into the source code, I have noticed some very interesting
"constructions" in the ThreadPool class. Namely, the setters for the
maxThreads, maxSpareThreads and minSpareThreads are having very little
influence as the start() method is resseting the values to the default
constants ?!?!
public ThreadPool() {
maxThreads = MAX_THREADS;
maxSpareThreads = MAX_SPARE_THREADS;
minSpareThreads = MIN_SPARE_THREADS;
currentThreadCount = 0;
currentThreadsBusy = 0;
stopThePool = false;
}
public synchronized void start() {
stopThePool=false;
currentThreadCount = 0;
currentThreadsBusy = 0;
maxThreads = MAX_THREADS;
maxSpareThreads = MAX_SPARE_THREADS;
minSpareThreads = MIN_SPARE_THREADS;
adjustLimits();
openThreads(minSpareThreads);
monitor = new MonitorRunnable(this);
}
Also, the situation when there are no more available Threads in the pool is being
handled in a special way which JUST BLOCKS IN THE INFINITE LOOP :
-(((
Is the code of the Tomcat4 equaly immature or there is a fair chance to
role a productiv system on top of it?
Thanks in advance for any comments
Drasko Kokic
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
