ForgeRock Identity Platform
Does not apply to Identity Cloud

Outdated JSP pages causing problems after upgrading AM (All versions)

Last updated Jan 16, 2023

The purpose of this article is to provide assistance if you are experiencing issues caused by outdated JSP pages after upgrading AM on Apache Tomcat™.


You see old JSP pages instead of the updated ones, even after a restart.

You may see failures due to old JSP pages calling out-of-date classes.

You notice traces of the old deployment even though you have upgraded.

Recent Changes

Upgraded AM.


The Tomcat cache has stored old JSP pages and is using them instead of the updated versions. This can happen if your server clock is wrong, causing the new JSP pages to have an older timestamp than the cached pages.


This issue can be resolved by clearing out the Tomcat cache and correcting your server clock.

You can clear out the Tomcat cache as follows:

  1. Make a backup of the files in the following work directory: /path/to/tomcat/work/Catalina/localhost/openam
  2. Stop the server.
  3. Delete the files in the work directory: $ rm -rf /path/to/tomcat/work/Catalina/localhost/openam
  4. Restart the server.

See Also

FAQ: Upgrading AM

Related Training


Related Issue Tracker IDs


Copyright and Trademarks Copyright © 2023 ForgeRock, all rights reserved.