Hi,
Has anyone been able to solve or work around this
problem under Tomcat 3.2.1? or does Tomcat 4.x
eliminate the pool exhausted problem?
We are running a medium load ASP and run into this
problem on 1 out of 4 servers each day, even though
we restart Tomcat nightly in effort to avoid it.
Ideally we wouldn't have to restart Tomcat more than
once every 2-3 weeks.
Any help much appreciated,
Matt
> At 12:56 PM 9/5/2001, you wrote:
> >Hello,
> >
> >We are seeing many many 'ThreadPool: Pool exhausted
> with 100 threads'
> >errors. Ive seen that you can modify the
> server.xml
> to customize threadpool
> >access (max_threads value=x max_spare_threads
> vaule=x, min_spare_threads
> >value=x), but Ive also heard that its hard coded in
> >org.apache.tomcat.util.ThreadPool.java in Tomcat
> 3.2.2. This is our
> >production env so Id hate to impliment this and
> have
> the prolem become
> >bigger. What do you guys suggest? We are using
> Tomcat 3.2.2, Apache 1.3
> >(with ssl mod) as our webservers, on Solaris 7,
> with
> Oracle 8 via jdbc.
>
> You could up the values and re-compile.
>
>
>
>
>
> _______________________________
> Do you Yahoo!?
> Win 1 of 4,000 free domain names from Yahoo! Enter
> now.
> http://promotions.yahoo.com/goldrush
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
