> I do have all the latest jar files from SUNW, and jakarta-apache. So I
> don't know what the problems could be. My only complaints would be not
> enough debug tools around to be able to single step through new code
> when you are having problems, but I consider that minor at this point,
> given where the tomcat development cycle is.
I've investigated a LOT of reported Tomcat "bugs" where I work that turned
out to be garden-variety bugs in the application (apps not dealing correctly
with bad data, apps exiting the JVM because something unexpected happened,
etc.).
The only issue we've found that didn't appear to be an application bug was
one where CPU usage trended to 100% over the span of an hour or so. This
was on Tomcat 3.2.1/Solaris ?/JDK 1.2.?. The problem vanished when we
switched the environment to JDK 1.3. Given that, we never did take the time
to figure out the exact problem.
Anyhow, the jdb debugger that is included with jdk 1.3 works pretty well for
debugging servlet/JSP code when nothing else is available. The command
interface takes a few minutes to understand, but it does get the job done.
And of course, to debug JSP code, you really have to go after the generated
servlet.
It's not pretty, but it does work.
During development, a lot of people around here use JBuilder to
develop/debug JSP and servlet code. It works well for us.
