Changes to JSP files require an application restart to take effect in RSA Identity Governance & Lifecycle

2 years ago

Originally Published: 2019-05-03

Article Number

000041077

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1

Issue

If an uploaded JSP file exists in the user interface (Admin > User Interface > Files) and a new or modified version of that same JSP file is uploaded, the changes specified by the newer JSP file are not reflected until after the RSA Identity Governance & Lifecycle application is restarted.

Cause

This is a known issue reported in engineering tickets ACM-88580 and ACM-99174.

Resolution

This issue is resolved in the following RSA Identity Governance & Lifecycle patch levels:

RSA Identity Governance & Lifecycle 7.0.2 P14
RSA Identity Governance & Lifecycle 7.1.0 P07
RSA Identity Governance & Lifecycle 7.1.1 P02

After upgrading to one of these patch levels or higher, an application restart will no longer be required for these changes to take effect.

Workaround

The workaround is to restart the RSA Identity Governance & Lifecycle application: As the oracle user, run:

$ acm restart

A modification was made to 7.0.2 P24, 7.1.0 P07 and 7.1.1 P02 that added the following error message to the user interface when uploading a newer version of the same JSP file:

After uploading a modified file that already exists in the system, restart the server to apply the changes. You can update custom string properties, security files and style sheets without a server restart.

Once you upgrade to the patches specified in the Resolution section, this workaround will no longer be needed.

Notes

Don't see what you're looking for?

Related Articles

Trending Articles