Hello all,
Recently we decided we need a Java application, to be used with the Tomcat
servlet engine. I had heard a few good things about IBM's JDK, so I went
with that. This was a few weeks ago, and I chose tomcat 3.2.2 (the most
recently available). The application (not written by me or my company)
seemed to work fine, except, in use it would get slower and slower, until
eventually a request would timeout, and the application would be
unreachable. I tried various different changes, the major one being
switching to Sun's JDK, but that didn't seem to help matters any.
Last week, when tomcat 4.0 was released, I quickly installed that on our
test machine. Other than a minor problem with the PrintWriter call,
everything seemed to work smoothly. No more slowness, and everything
seemed fine (I should mention this is after having switched back to IBM's
JDK). However, after some undetermined length of time, tomcat 4 seems to
simply stop responding to requests. Telnetting to port 8080 and just
issuing a 'GET / HTTP/1.0' results in no response from the server at all.
Here are the specs of my environment:
2x400mhz PII processors
648mb ram
kernel 2.2.18 SMP
IBMJava2-SDK-1.3
Tomcat 4.0
glibc 2.1.3-22 (from redhat)
Also, when the system is in this state, nothing gets written in any log
file, except for this in the catalina log:
2001-09-24 10:46:47 HttpProcessor[8080][20] Starting background thread
2001-09-24 10:57:54 HttpProcessor[8080][21] Starting background thread
for each request, one of those will show up in the log, but nothing else
will happen.
Can anyone shed some light on this, or point me at a resource that might
help? Could this be an smp problem? Should I switch to sun's JDK, or one
from blackdown.org? Is there some way i can make the JVM run only in
'uniprocessor' mode? Am I insane??? :)
Thanks!
-e
