Hello Marc (and others that have been so kind to help),
Here is the rundown on what I have tested:
* Running on a Quad Processor NT Enterprise 6 Sp6a
* This server is production - fairly static content
(w/no recompile)
* Verified thread deadlocking behavior on 2 different
multiprocessor servers running different apps.
Both servers have the same problem.
* Verified a single processor server running same
apps and an exact copy of Tomcat and the conf
files. No thread problem found.
* There are very few contexts, and all do exist
* Running both servers with ISAPI plugin behind IIS 4
* Currently running with sdk 1.2.2 (now testing 1.3.1)
* Both production servers are running with 128mb
allocated to the JVM via startup param. No
other startup params are used.
* Both servers run apps containing Javabeans, JSPs,
and Servlets. Javabeans do use a properties
class with a static class variables.
This issue has been very easy for us to reproduce. Thus,
I assumed this must be our error in some way. I am sure
many others are running Tomcat on multiprocessor NT servers?
I am very committed to Tomcat in my division and I am willing
to help out in any way I can. Please let me know if I can
provide any further assistance. In the mean time, I am going
to do the following:
1. Complete testing and port to 1.3.1
2. Install a thread monitor
3. Attempt to debug the source.
Thank you again for your assistance!
Joel Kozlow
