Admin Console does not come up wrong with ELF class: ELFCLASS64

Document ID : KB000117626
Last Modified Date : 16/10/2018
Show Technical Document Details
Issue:
CA strong Authentication Admin console does not come  up and logs shown that there are architectural mismatch issues.  At version 9.0 CA Strong Authentication installer when run on a 64-bit RHEL provides only a 64-bit version of libArcotAccessKeyProvider.so file. This file with the matching Java bit version (hence 64-bit version of libArcotAccessKeyProvider.so is required  with 64-bit version of Java)

========================================= Stack Trace that is posed on failure to deply ====================
Caused by: java.lang.UnsatisfiedLinkError: /usr/java/jdk1.8.0_181-i586/jre/bin/libArcotAccessKeyProvider.so: /usr/java/jdk1.8.0_181-i586/jre/bin/libArcotAccessKeyProvider.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch) 
========================================== =====================================================

1. The installer was run on a RHEL 64-bit machine. Hence CA Strong Authentication only contains  oNLY a 64-bit libArcotAccessKeyProvider.so in directory <ARCOT_HOME>\native\Linux\ 

2. Customer has deployed a 32-bit Java/JDK which requires 32-bit version of libArcotAccessKeyProvider.so


*** Note it is recommended that on a 64-bit RHEL server the Java of 64-bit be used and 64-bit libArcotAccessKeyProvider.so be used ****
Environment:
Linux Server (RHEL) running CA Strong Authentication or CA Risk Authentication version  9.0
Cause:
Architectural mismatch between the Java (32-bit Java in this case)  used and RHEL architecture being used (64-bit version in this case) 
Resolution:
1. Run the CA Strong Authentication installer (example CA-StrongAuthentication-8.2.1-Linux-Installer.bin) on a separate 32-bit  RHEL machine.

2. Since persisting with a 32-bit Java on a 64-bit RHEL machine copy the 32-bit libArcotAccessKeyProvider.so from the 32 RHEL machine in #1 above to the required location on RHEL 64 bit machine. 

3. Restart the application server on the RHEL 64 bit machine and the Admin Console should deply without issues. 
Additional Information:
None.