DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6594>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6594 Caching behavior after re-deploying a WAR with the manager Summary: Caching behavior after re-deploying a WAR with the manager Product: Tomcat 4 Version: 4.0.2 Final Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] After re-deploying a webapp (contained in a WAR), it seems to still use the previous version. This is the procedure that I followed: 1. http://localhost:8080/manager/remove?path=/mywebapp 2. overwrite original mywebapp.war with an updated version (contains a trivial comment change in the index.jsp - to test whether or not it's getting updated) 3. http://localhost:8080/manager/install? path=/mywebapp&war=jar:file:/path/to/mywebapp.war!/ When I load the webapp in a browser, it still shows the old index.jsp (e.g. the trivial comment change isn't showing up). I've tried a few different things like deleting the work/localhost/mywebapp/* and webapps/mywebapp/* to clear the cached unpacked war and any session data. But, I still get the same "cached" results. This only seems to occur when deploying WARs. When I deploy the webapp as a path to an unpacked WAR, re-deploys work fine. Prior to upgrading to Tomcat 4.0.2, I was getting a similar problem as that reported in Bug #5364, but now that problems seems to be fixed. Instead, I was the above problem remaining. Lastly, I'm running Tomcat 4.0.2 on RedHat Linux 6.2 with Apache 1.3.22 and mod_jk (AJP13). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
