Changing the maximum heap (Xmx) and minimum heap (xms) settings in wrapper.conf and setenv.bat files for SAS® Web Application Servers is not effective


You might encounter an issue in which changes you make to maximum heap (Xmx) and minimum heap (xms) settings in wrapper.conf and setenv.bat files for SAS Web Application Servers are not effective. 

Here are steps to replicate the problem:

  1. Change the minimum and maximum heap settings by changing the values in the wrapper.conf file under C:\SAS\Config\Lev1\Web\WebAppServer\SASServer1_1\conf.
  2. Rebuild the Windows Service after making these changes.
  3. Restart SAS Web Application Server.

In the server.log file, the following values are listed:

 

2023-06-02 14:10:52,198 INFO  (main) [org.apache.catalina.startup.VersionLoggerListener] Command line argument: -Xms4096m
2023-06-02 14:10:52,198 INFO  (main) [org.apache.catalina.startup.VersionLoggerListener] Command line argument: -Dcom.sas.server.isclustered=true
2023-06-02 14:10:52,198 INFO  (main) [org.apache.catalina.startup.VersionLoggerListener] Command line argument: -Xmx8024m
 

But, later in the same log, older values are also listed:

 

2023-06-02 14:10:52,204 INFO  (main) [org.apache.catalina.startup.VersionLoggerListener] Command line argument: exit
2023-06-02 14:10:52,205 INFO  (main) [org.apache.catalina.startup.VersionLoggerListener] Command line argument: abort
2023-06-02 14:10:52,205 INFO  (main) [org.apache.catalina.startup.VersionLoggerListener] Command line argument: -Xms1024m
2023-06-02 14:10:52,205 INFO  (main) [org.apache.catalina.startup.VersionLoggerListener] Command line argument: -Xmx4096m
 

This is a known issue for SAS® 9.4M8 on Microsoft Windows.

 

Workaround

  1. Stop SAS Web Application Server instances.
  2. Make backup copies of SASServiceCtl.ps1 in C:\SAS\Config\Lev1\Web\WebAppServer\SASServerN_M\bin\.
  3. Edit the original scripts. The following should appear:

  1. Comment out lines 769 and 770 ( --JVmMs and JvmMx by adding a # before them - as shown in the screenshot above).
  2. Uninstall and reinstall Windows services.

After these steps, the JVM minimum and maximum heap settings that you set in wrapper.conf and setenv.bat files should appear.