Unexpected termination can occur for SAS solutions or SAS Web Application Servers as a result of Java process termination on Oracle or Zulu Java virtual machines (JVMs) in Linux operating environments.
If you experience this problem, contact SAS Technical Support for help. You should collect and send the following items to Technical Support:
- the hs_err log: The actual name of the file depends on what the process ID is for the Java process. For example, if the process ID of the Java process is 123456, the log file name is hs_err_pid123456.log, by default.
- Locate the hs_err log, which resides in the SAS-configuration-file/LevN directory.
- Run the following TAR command to retrieve all the shared libraries that are listed in the hs_err log file:
tar cvfz libs.tar.gz $(grep "\.so" <hs_err file> | awk '{print $NF}' | sort | uniq)
If you need to move the hs_err file to another location to avoid a risk to production systems, you can do that by using the option ErrorFile. For example, you can apply the following command as a Java command-line argument:
-XX:ErrorFile=/tmp/hs_err_pidprocess-ID-number.log
- core file: The actual name of this file also depends on what the process ID is for the Java process. For example, if the process ID is 123456, the file name is core.123456.log. This file also resides in the SAS-configuration-file/LevN directory.
- the libs.tar.gz file: This file resides in a directory of your choosing.