This SAS KB article leads you through steps for collecting the must-gather data that is required to investigate the root-cause analysis of performance degradation within the SAS Risk Governance Framework Web application.
Step 1: Gather Information That Is Related to the SAS® Deployment
1. Collect SAS View Registry Tool output from the middle-tier machine, as described in SAS KB0036131, "Using the ViewRegistry Report and other methods to determine the SAS® 9.2 and later software releases and hot fixes that are installed."
2. Provide additional information about the exact content-package solution release that is deployed in the problematic SAS Risk Governance Framework environment. (Examples of the content-package solution releases are CECL, IFRS, RRM, GCM, Risk Stratum, and so on.)
3. Answer these questions:
-
- Are all SAS Risk Governance Framework users observing the performance lag, or does the lag occur for specific users only?
- When performance problems occur, can you access other SAS® web applications (for example, SAS® Visual Analytics Hub or SAS® Studio) without any issues?
- Is there any specific action or task (for example, navigating through pages) where users notice slow performance?
Step 2: Gather Information That Is Related to the Operating System
Collect output for the commands listed below for the middle-tier server that is deployed on your particular operating system:
For Microsoft Windows Operating Systems
systeminfo | find "Available Physical Memory"
netsh int ipv4 show dynamicport tcp
netsh int ipv4 show dynamicport udp
netsh advfirewall show allprofiles firewallpolicy
For the Linux Operating System
iptables -L -n
ifconfig -a
free -g
cat /etc/sysctl.conf
cat /etc/security/limits.conf
cat /etc/security/limits.d/*-nproc.conf
cat /proc/sys/kernel/pid_max
cat /proc/sys/net/ipv4/ip_local_port_range
cat /proc/sys/net/ipv4/tcp_fin_timeout
cat /proc/sys/net/core/netdev_max_backlog
cat /proc/sys/net/core/somaxconn
cat /proc/sys/net/ipv4/tcp_keepalive_intvl
cat /proc/sys/net/ipv4/tcp_keepalive_probes
Step 3: Enable Debugging for the SAS® Risk Governance Framework Performance Issue
Perform the following must-gather steps to enable debugging for the control SQL:
1. Using a WebDAV client tool or the WinSCP client, connect to the SAS Content Server WebDAV Repository via the URL below:
RiskGovFrwkMid-Tier/rgf-system/Config
2. For the SAS Risk Governance system in the WebDAV repository, locate the system.properties file that reside in the Config/ folder, as shown below:
3. Locate the parameter monitor.db.show_sql value in the system.properties file and set the value to true.
If you do not find the parameter in that file, manually add it to the bottom of the file.
Note: For more details about this file, see the section "Updating Configuration Files" in the SAS® Risk Governance Framework 7.4: Installation and Configuration Guide
4. Stop and restart the SASServer8_1 web application server only so that the change in step 3 takes in effect. The commands to stop and restart the server in UNIX operating environments are shown below:
SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer8_1/bin/./tcruntime-ctl.sh start
Note: The steps above will cause the SAS Risk Governance Framework log file to become larger than usual. So, be aware of that and monitor the amount of free space that you have.
Step 4: Enable Debugging for the SAS® Risk Management UI Performance Issue
Perform the following must-gather steps to enable debugging for UI performance issues:
1. Enable the following debug logging in the SASRiskGovernanceFrameworkMidTier-log4j.xml file that resides in SAS-configuration-directory\Lev1\Web\Common\LogConfig\, as shown below:
<category additivity="false" name="com.sas.oprisk.server.perf" >
<priority value="DEBUG" />
<appender-ref ref="SAS_CONSOLE" />
<appender-ref ref="SAS_FILE" />
</category>
</sasconfig>
2. Restart SASServer_8.1.
3. Reproduce the issue and collect a network trace, as described in SAS KB0036430, "Using the web browser developer tools to investigate issues in SAS® Web Applications."
4. Send the following items to SAS Technical Support:
- a screen capture of the cycle, along with the URL
- the HAR file from the network trace
- the SASRiskGovernanceFrameworkMidTier.log file that resides in the SAS-configuration-directory\Web\Logs\SASServer8_1\
Step 5: Gather Information for Performance Issues That Are Related to Nonresponsive Java Virtual Machines (JVM) and High CPU Usage
Collect additional CPU and thread-dump data and sent it to SAS Technical Support, as explained below.
-
- For Microsoft Windows operating environments: Collect JVM performance data by using the JVisual VM, as described in SAS Note 42373, "Using the jvisualvm tool to remotely monitor a Java virtual machine."
- For the Linux operating environment: Collect JVM performance data, as described in SAS Note 50330, "Collecting artifacts in the Linux operating environment in order to troubleshoot problems with your web application server."