I apologize, I mistakenly sent my message 3 different times. When my first post did not arrive within 2 hours, I assumed there must be security restrictions on which mail accounts can post messages. Thus, I tried again with a different account. This was entirely my error....sorry :) -----Original Message----- From: midian [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 22, 2001 9:40 AM To: '[EMAIL PROTECTED]' Subject: Thread deadlocking in 3.2.2 beta 5? Hello, I have an app I just ported to Tomcat 3.2.2 beta 5 that runs fine for a while, and then begins to run slower and slower until it dies. From looking at the log files, it appears that 3.2.2 beta 5 is thread deadlocking and thus running out of resources. The log file shows "Full thread dump..." sections where you can see the JVM is having problems releasing threads. The really weird thing is that this is not a high volume server. It received no more than 300 hits over the period of a week. However, that was enough traffic to kill it. I have the same exact app running on another machine under 3.2.1 with no problems. If you look at the log file on the 3.2.1 machine, there are no "Full thread dump..." errors and the app has been up for months. Thus, something appears to have changed between these versions that is affecting my app's thread usage. There are a few environmental differences between the two implementations of Tomcat. I have 3.2.2 beta 5 on a quad processor WinNT 4 Sp6a machine w/128mb allocated to Tomcat. 3.2.1 runs on a single processor Win2K server w/64mb allocated to Tomcat. Could the multi-processor server be a factor? Both servers are using Sun JDK 1.2.2. Since the log file to 3.2.2 beta 5 is so big, I have posted it to the URL : http://www.poptarantula.com/logs/jvm.stderr_5_22_01.txt Does any one have any idea what could be causing this behavior? Are there any known fixes? Thank you in advance for your help. Best regards, Joel Kozlow [EMAIL PROTECTED] Sn. Developer Hewtlett-Packard