000030547 - Unable to access IMG application UI after upgrade to 691

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

Article Content

Article Number000030547
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Appliance
RSA Version/Condition: 6.9.1
Platform: Linux
Platform (Other): null
O/S Version: Red Hat Enterprise Linux 5.x
Product Name: null
Product Description: null
IssueA Customer successfully upgraded (ie there were no errors seen in either the migrate.log nor the aveksa-install.log files - see notes for complete path to these files) from ACM 6.5.2-P03 to IMG 6.9.1 GA. After the upgrade, they were not able to access the application UI  - instead an Initialization error was seen in the browser and in the aveksaServer.log:
****************************************
Initialization has failed!
Unable to start service CertificateService. java.lang.NoSuchMethodError: com.rsa.asn1.OIDContainer.<init>(IZILjava/lang/String;I)V
****************************************
Further, an additional application stacktrace and application error are seen in the aveksaServer.log:
06/10/2015 09:46:35.569 INFO  (main) [com.aveksa.server.certificates.CertificateManager] Creating X509Certificate for localhost.localdomain
06/10/2015 09:46:35.674 ERROR (main) [com.aveksa.server.core.Container] Unable to start service CertificateService. 
java.lang.NoSuchMethodError: com.rsa.asn1.OIDContainer.<init>(IZILjava/lang/String;I)V
    at com.rsa.cryptoj.o.bk.a(Unknown Source)
    at com.rsa.cryptoj.o.bk.a(Unknown Source)
    at com.rsa.cryptoj.o.bk.a(Unknown Source)
    at com.rsa.cryptoj.o.fr.getEncoded(Unknown Source)
    at com.aveksa.server.certificates.CertificateManager.createCertificate(CertificateManager.java:128)
    at com.aveksa.server.certificates.CertificateManager.createCertAndKeyStore(CertificateManager.java:347)
    at com.aveksa.server.certificates.CertificateManager.createClientKeyStore(CertificateManager.java:425)
    at com.aveksa.server.certificates.CertificateManager.createClientKeyStore(CertificateManager.java:409)
    at com.aveksa.server.certificates.CertificateManager.createClientKeyStore(CertificateManager.java:393)

and
06/10/2015 09:46:36.895 INFO  (main) [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 57s:454ms
06/10/2015 09:46:36.938 ERROR (http-0.0.0.0-8445-3) [com.aveksa.UI] com.aveksa.gui.core.ACMLoginLogout.getSessionIdHash(ACMLoginLogout.java:720) - Failed to get hash value of the session Id
com.rsa.jsafe.JSAFE_UnimplementedException: A JSAFE_MessageDigest object of SHA256 is not available on any of the devices. (Java)

 
CauseThe class method identified in the stack trace, java.lang.NoSuchMethodError: com.rsa.asn1.OIDContainer, is an indicator that the jboss server code is still executing and the application code has not yet been 'called'.
The most likely case for this that one or more jar files that were installed during the upgrade are not correct.  It is probable that one or more .jar files are 'corrupted' or are inaccessible in some fashion (incorrect file ownership and/or file permissions),  This will be more evident if the sizes and file ownership is not correct.  It may even  be possible to identify which jar files are invalid.   However, this is not always possible to confirm.

 
ResolutionThe preferred resolution is to uninstall and re-install the version that was upgraded to - in the above scenario, this would be IMG V6.9.1 GA
After confirming that the installation .bz2 file could be read, the installation files were extracted, the existing 'bad' installation was removed by running /tmp/aveksa/staging/deploy/uninstall.sh, as the Linux root user.
After the uninstall.sh was completed, the application was installed by running /tmp/aveksa/staging/install.sh, per the IMG Installation guide, the jboss server started correctly and the application UI was accessible.
WorkaroundIdentifying problematic .jar files and replacing them can be tried, but the best, most efficient and sure action is to uninstall and re-install the IMG application.
NotesLocation of files referenced:
IMG installation log:  /tmp/aveksa-install.log
IMG migration log:    /home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/database/log/migrate.log
IMG application log:  
/home/oracle/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServer.log

Attachments

    Outcomes