While I was writing the following I changed reloadable to "false" in the context and the problem went away. I'll post this message anyway, someone else may find this info useful. In this case just kicking the problem around with others was what was needed. Thanks for the replies. I have one more issue to post and then maybe I can help someone else.

****************
I changed the Loader Properties/Check Interval in the Admin tool to 300 saved it (couldn't find where) reset the server, restarted tomcat and it had changed back to 15.

In the meantime I found this
http://java.sun.com/webservices/docs/1.1/tutorial/doc/Admintool4.html#wp69103

and this
http://www.jguru.com/faq/view.jsp?EID=1027658

this in web.xml for the Tomcat Server
<!-- The JSP page compiler and execution servlet, which is the mechanism -->
<!-- used by Tomcat to support JSP pages. Traditionally, this servlet   -->
<!-- is mapped to URL patterh "*.jsp". This servlet supports the      -->
<!-- following initialization parameters (default values are in square   -->
<!-- brackets):                                       -->
<!--                                               -->
<!--  checkInterval     If development is false and reloading is true, -->
<!--               background compiles are enabled. checkInterval -->
<!--               is the time in seconds between checks to see  -->
<!--               if a JSP page needs to be recompiled. [300]   -->

and I remember somewhere in the documentation a discussion of changes to Tomcat between development and production environments, and the defaults.

So, maybe everything is working exactly as it is configured, or something is causing Tomcat to think that JSPs have been modified.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)