Issue

In SAS^® 9.4 M7 (TS1M7) Rev. 940_22w08 and later, the sas.servers script that starts the SAS web application server for SAS Fraud Management 6.1 might not detect when the start-up process is complete. Instead, the script waits for approximately 27 minutes before continuing. This issue does not impact the actual start time of the web application server. Users can log in to SAS Fraud Management even though the sas.servers script continues to wait. 

The messages to the console appear as follows:

Workaround

To determine whether this workaround can be used in your environment, verify that SAS-configuration-directory/Levn/Web/WebAppServer/SASServer8_1/log4j2 directory exists. If this directory exists and contains the log4j2.xml file, you can use the following steps as a workaround.   

Note: These steps assume that the SAS Fraud Management application is installed on the SASServer8 web application server.  

1. Save a copy of the setenv.sh file located in SAS-configuration-directory/Levn/Web/WebAppServer/SASServer8_1/bin directory.
2. Edit the setenv.sh file to add the following option to the end of the JVM_OPTS line. This option needs to be placed inside the closing double quotation marks. You must replace the <impl-name> placeholder with the correct value for your environment.

3. Restart the SASServer8 web application server.