000011612 - RSA Deployment Manager 1.3.1 - Cached class files not regenerated even after reboot.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011612
Applies To
RSA Deployment Manager 1.3.1

Microsoft 2003 SP3 server.
Modified a Java Servlet Page that caused catastrophic failure and now need to revert back to original saved page.

Wbur Debug LOG shows a jdbc failure to connect to database, along with a host of application level failures. Customer had swapped out the standardTemplate.jsp page with one modified by them. This files exist in the RSASWE\jsp folder. The original standardTemplate.jsp was put in place and the RSA Web Service was restarted. The replacement page was still being accessed by the application and the failure persisted. The system was rebooted with the same results.
When the custom JSP was put in place the java class file was recompiled. It was not after putting the original file back in place. Tomcat continued to serve up the bogus custom java class file.
Stop the RSA Web Service.

Make sure the good standardTemplate.jsp is in place, \ RSA Security\RSA Web Service\Tomcat\webapps\RSASWE\jsp\standardTemplate.jsp.

Rename the folder \ RSA Security\RSA Web Service\Tomcat\work\Catalina

Start the RSA Web Service

You will find the Catalina folder is recreated and newly compiled java class files exist in the folder \ RSA Security\RSA Web Service\Tomcat\work\Catalina\localhost\RSASWE\org\apache\jsp. The original standardTemplate.jsp was recompiled and the Deployment Manager is once again functional.
Legacy Article IDa56082