Pascal,
Our connectionTimeout value is set to the Tomcat default of 60000 (60
seconds). I'm not exactly sure how to determine if that's too high?
Any ideas? Also, we're around 30-40 concurrent users during our peak
times of day but that's about it. The server load is OK... I mean right
now when I do a thread dump it shows 540 threads but our available mem
on the server is still fine (and relatively unchanged since we started
the service) and the CPU is about 90% idle. The thread count just climbs.
We did hear about trying to set the LD_ASSUME_KERNEL parameter to 2.4.1
to use the older Linux threads library which has seemed to help. A
couple of days ago we removed that parameter and had Tomcat set to 500
for maxProcessors and we ran out of threads in approx 5 hours. I set
the LD_ASSUME_KERNEL to 2.4.1 and it has curbed how fast the threads are
being used but the thread count is still increasing... just not as fast.
-Derek
Pascal Alberty wrote:
Check your connectiontimeout value. May be it is too high ?
Have you a heavy load on this server ? How many (concurent) users ?
On 10/18/06, Derek Wormdahl <[EMAIL PROTECTED]> wrote:
We initially started this project running on the Sun JVM but ran into an
issue with the JVM aborting when doing a PDF conversion in the
application. Some conflict with the iText libraries or something.
JRockit was the only JVM that seemed to not have the problem. We
haven't tried the Sun JVM since we've noticed these issues but it may be
a tradeoff we need to make in order to see if the problem persists. So
do you think it's more likely a JVM bug/issue opposed to an application
issue?
Thanks,
-Derek
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
