|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle|
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.1.1, 7.1.2
|Issue||After upgrading to RSA Identity Governance & Lifecycle 7.1.1 and higher, pages or tabs that are based on custom JSP code fail to display.|
The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) has jasper exception errors such as JBWEB004062 and JBWEB004060. The actual contents of the error messages vary depending on what JSP file has been customized but the general format of the errors are:
where ## is the line of code where the failure occurred.
Please refer to RSA Knowledge Base Article 000030327 -- Atifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
|Cause||In general the BWEB004062 error means that some aspect of the custom JSP cannot be compiled.|
The JBWEB004060 failure is specifically due to calling the isSinglePage function which has been deprecated in RSA Identity Governance & Lifecycle 7.1.1 and higher.
The isSinglePage function was required on earlier versions of RSA Identity Governance & Lifestyle to ensure that the content was served in a single page. This was due to the multiple user interface styles available in the older versions. The old user interface styles have been removed in 7.1.1 and above so this flag is no longer needed.
|Resolution||To resolve this issue, remove the isSinglePage references in the custom JSP code and recompile.|
|Notes||If you need assistance with the design of custom JSP pages, the RSA Professional Services team can provide assistance. Please contact RSA Identity Governance & Lifecycle Support who can open a case for you with the RSA Professional Services team.|