It's not a secret anymore!
The moose likes Tomcat and the fly likes 500.jsp is out of date after changing content Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Introducing JavaFX 8 Programming this week in the JavaFX forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "500.jsp is out of date after changing content" Watch "500.jsp is out of date after changing content" New topic
Author

500.jsp is out of date after changing content

pakse delegsol
Greenhorn

Joined: Dec 02, 2013
Posts: 1
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

Joined: Jun 25, 2001
Posts: 17142
    
  27

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.


An IDE is no substitute for an Intelligent Developer.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: 500.jsp is out of date after changing content
 
It's not a secret anymore!