000029317 - LaunchAnywhere IllegalArgumentException with AxM 6.2 installer

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 Number000029317
Applies ToRSA Product Set: ClearTrust
RSA Product/Service Type: Access Manager
RSA Version/Condition: 6.2
Platform: Linux
Platform (Other): null
O/S Version: Red Hat Enterprise Linux 6.x
Product Name: RSA-0010020
Product Description: Access Manager
Issue

The RSA Access Manager installer fails with the following exception:


An internal LaunchAnywhere application error has occured and this application cannot proceed. (LAX)
Stack Trace:
java.lang.IllegalArgumentException: Malformed \uxxxx encoding.
        at java.util.Properties.loadConvert(Unknown Source)
        at java.util.Properties.load0(Unknown Source)
        at java.util.Properties.load(Unknown Source)
        at com.zerog.common.java.util.PropertiesUtil.loadProperties(DashoA10*..)
        at com.zerog.lax.LAX.<init>(DashoA10*..)
        at com.zerog.lax.LAX.main(DashoA10*..)



 


The zerog debug output shows that the installer is attempting to launch java with the following command line:


+ exec /tmp/install.dir.10005/Linux/resource/jre/bin/java -Djava.compiler=NONE -Xmx50331648 -Xms16777216 com.zerog.lax.LAX /tmp/install.dir.10005/temp.lax /tmp/env.properties.10005

CauseThe installer creates a temporary file that it passes on the java command line called env.properties file in the /tmp/ directory.   If there are any escaped characters in this file such as "\u" the java application incorrectly attempts to interpret them as extended encoded characters.  This causes the java application to fault.  The exact character that causes the fault may vary.   The most common place for the character to exist is in the definition for the UNIX environment variables such as those used to define the command prompts for the shell.  For example
MYSQL_PS1=(\u@\h) [\d]> 
 
ResolutionThis is a known issue in early versions of the LaunchAnywhere installer.   This issue is resolved in later versions.  RSA does not patch installer packages so this issue will be addressed in the next version of the product. 
WorkaroundInspect the /tmp/install.dir.10005 file (the number may not be 10005 in each instance) and identify any character sequences that are being interpreted as extended characters.  Temporarily remove or rename the problem UNIX environment variable to allow the installer to complete.

Attachments

    Outcomes