Useful Hint for Dealing with Tomcat Issues

This post is more than 2 years old.

So, I'm still kinda new at this Java thing. I'm working on my first real JSP based web site, and ran into a problem that I couldn't fix today. The only change I had made in the past week was to update the Java SDK from 1.3.x to 1.4.x. What I forgot - though - was that I had many JSP files already compiled by Tomcat. My coworker AJ pointed out that I should delete the compiled files in my work directory. So - I did that - and restarted - and it worked perfectly. I also remember this suggestion from others in the past.

So - in the hopes of helping others, I'm passing it on here.

Raymond Camden's Picture

About Raymond Camden

Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support. You can even buy me a coffee!

Lafayette, LA

Archived Comments

Comment 1 by Aaron Johnson posted on 3/22/2003 at 2:19 AM

from the Tomcat 3.2 docs available here (

"<i>6.4 Automatic Servlet Reloading

Tomcat 3.2 includes a feature whereby you can ask it to automatically reload servlet classes (loaded from either the WEB-INF/classes directory
or a JAR file in the WEB-INF/lib directory) that have been changed. This feature is experimental, and may not be completely functional. In particular, changes to classes other than the servlet you are requesting do not trigger class reloads -- you will need to restart Tomcat to reflect changes in those classes.</i>"