Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

500.jsp is out of date after changing content

 
pakse delegsol
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
for Tomcat 7.0.47 in combination with IIS7 on Windows I defined an error page 500.jsp that way in web.xml
<error-page>
<error-code>500</error-code>
<location>/cms/500.jsp</location>
</error-page>

It works fine, when error 500 is thrown I see the content of 500.jsp.
But after changing the content of 500.jsp I still see the old content of 500.jsp.

The .java/.class files generated under Tomcat works are more or less the same date as the .jsp file.
Tomcat was also restarted several times.

Tests:
Call http://localhost/cms/500.jsp -> okay, I always see the new content of 500.jsp
Call http://localhost/cms/error.jsp -> test page throws an error 500 and I see the old 500.jsp

Any idea what it is ?

Best regards
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18096
50
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the JavaRanch, Pakse!
Try this:

1. Halt Tomcat.
2. Delete everything in the Tomcat "work" directory. Just for fun, also delete everything under the "temp" directory as well.
3. Restart Tomcat.

This usually will be sufficient to purge stale JSPs. If that doesn't help, you might have stuff in your client browser cache that needs to be flushed out.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic