BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Quartz | Level 8

Hi. Thanks for you answer.

This is the full command for the Java prcess that takes most of CPU (the line highlighted in blue):


Let me know if you can read it. (righ click and open in new tab)

And your other questions:

  • Yes we use AUTOLOAD but there are only a few data sources and they have been there for a long time. 
  • There is only one server for SAS VA afaik.


I also got a much better reply from SAS Support so I paste it below:

The JAVA memory use should on the other hand be related to WEB server activities

(I will check with some technical staff on this)

By the way could you check the following folder:

C:\SAS\Config\Lev1\Web\activemq\data - it should only contain 4 objects and the kahadb-folder content should be of current date and reasonable in size.


When I look at the kahaddb folder there is a log file called db-729.log that is about 32 MB. This file is used by Java and I need to stop the services in order to make any changes. Is this an unusual size for the file? Should I try getting a back up and replacing it with an empty one?

Amethyst | Level 16



now it is clear to me that the problem is not on autoload, only the web application server, actially only on the SASServer1_1. And I know this problem, happens specially on the SAS Content Server and SAS Logon.


We are getting there.


Some more questions:

- Do you have only SASServer1_1 or also SASServer2_1 and SASServer12_1?

- Do you have enabled the Audit and Performance reports on VA? (So you have an AUDIT_ARTEFACTS table being created and loading into memory)? And you do, how big is this table at this moment?

- could you please share the JVM settings you have on the wrapper.conf on the SASServer1_1? (if you have more than 1_1, I would like to give a look into those).


Thank you in advance!

Looking forward for your feedback

Quartz | Level 8

Hi again,

  • There is only one web app in my services and that is SASServer1_1 - WebAppServer,
  • I doubt if there are any audits. At least I do not seem to find the audit_visualanalytics.sas7bdat file in my entire SAS folder.
  • This is the content of my wrapper.conf located in the sashome folder.
# Java Application\sas\sashome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe

# Java Classpath (include wrapper.jar)  Add class path elements as
# needed starting from 1\sas\sashome\SASVersionedJarRepository\eclipse\plugins\JavaServiceWrapper_3.2.3\wrapper.jar\sas\sashome\SASVersionedJarRepository\eclipse\plugins\sas.launcher.jar

# Java Additional Parameters"E:\sas\sashome\SASVersionedJarRepository\eclipse"
Obsidian | Level 7
As @JuanS_OCS mentioned you might to focus on the Java heaps etc.

The audit analytics table will be under emdbla folder if you have enabled the load.

You might want to check the total time spent in garbage collection etx. Easiest way is to enable the auto load for va feed on emi frame work and you have default dashboards provided by sas one is for the application monitoring and another is for va usage.

Under application monitoring you might want to focus on app response time.

Best regards,
Sai korrapati
Sai Korrapati
Quartz | Level 8

I am sorry, but could you be a little more specific like @JuanS_OCS? I haven't enabled AUDIT. And my SAS VA is currently too slow for me to start building reports for monitoring. 


Kind regards,


Amethyst | Level 16

Hey there,


sorry, what i need is the wrapper.conf under /Config/Lev1/Web/WebAppServer/SASServer1_1/conf. You should find some lines with information such as:

How many cores do you have on the server (logical or virtual), which speed and how much RAM memory?


Now, and as heads up of what my advise will be based on:


SAS recommends (by default) on Single Web App Server ( ) the following values. But you should extend them until the performance is good again. I have on some systems values of 20480m for Xms and Xmx and 2048 for PermSize and MaxPermSize. You should start with the recommended values, and then start to make them grow. After each change, you will need to restart the SASServer1_1 service (do not forget to clean or achive and clean SASServer1_1/tmp, SASServer1_1/work and SASServer1_1/logs after stoping and before starting the SASserver1_1:





SharedServices JDBC Resource 



Tomcat Executor Thread Pool




More things you can do to tune your system:


Operating System:


And those other two, which can be found under:


PS. What @userid007 whanted to mention is the SAS Environment Manager metrics:




Quartz | Level 8

I see. I paste the wrapper.conf content below. I'm now going to read your entire message.

# Wrapper Properties

# Java Main class.  This class must implement the WrapperListener interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.

# Java Home

# Java Additional Parameters"-Djava.endorsed.dirs=%CATALINA_HOME%\common\endorsed""-Dcatalina.base=%CATALINA_BASE%""-Dcatalina.home=%CATALINA_HOME%""\temp""file:///E:/sas/config/Lev1/Web/Common/LogConfig""E:/sas/config/Lev1/AppData/SASContentServer/Repository"[41415]"E:/sas/sashome/ReportFontsforClients/9.4""E:/sas/sashome/SASVisualAnalyticsPrintingSupport/7.3""E:/sas/config/Lev1/Web/Logs/SASServer1_1""E:/sas/config/Lev1/Web/WebAppServer/SASServer1_1/conf/jaas.config""E:/sas/config/Lev1/Web/WebAppServer/SASServer1_1/sas_webapps""E:/sas/sashome/SASRemoteDeploymentAgentClient/2.1/config/""E:/sas/sashome/SASVersionedJarRepository/eclipse"

# Java Library Path\bin\winx86_64

# Java Classpath\bin\winx86_64\wrapper.jar\bin\winx86_64\threaddumpwrapper.jar\bin\bootstrap.jar\bin\tomcat-juli.jar\lib\log4j.jar\lib\conf\..\lib\tools.jar

# Java Application\sas\sashome\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java.exe

# Application parameters.  Add parameters as needed starting from 1
# The first application parameter is the name of the class whose main
# method is to be called when the application is launched.  The class
# name is followed by the number of parameters to be passed to its main
# method.  Then comes the actual parameters.



# Wrapper Logging Properties
# Format of output for the console.  (See docs for formats)

# Log Level for console output.  (See docs for log levels)

# Log file to use for wrapper output logging.

# Format of output for the log file.  (See docs for formats)

# Log Level for log file output.  (See docs for log levels)

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.

# Log Level for sys/event log output.  (See docs for log levels)

# Wrapper Windows Properties
# Title to use when running as a console

# Wrapper Windows NT/2000/XP Service Properties
# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Service dependencies.  Add dependencies as needed starting from 1

# Mode in which the service is installed.  AUTO_START or DEMAND_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false is set in the tcruntime-ctl.bat script [config-Lev1] SASServer1_1 - WebAppServer
wrapper.ntservice.displayname=SAS [config-Lev1] SASServer1_1 - WebAppServer
wrapper.ntservice.description=SASServer1_1 WebAppServer at config-Lev1 on port 8080
Amethyst | Level 16

I see. You probably have too low values on your Java Virtual Machine for the SASServer1_1, therefore probably your java process is taking long time just collecting garbage. If you extend the values as SAS recommends probably will have a good start by itself. But it will depend a lot on your hardware capabilities: RAM and CPU/cores.

Quartz | Level 8
I am just a step away from restarting the services. One quick question: Should I archive the entire SASServer1_1/work folder and then clean it just like the temp and the logs folder?
Amethyst | Level 16

No, work and tmp you can clean directly. And logs it is up to you to first archive them, or clean them directly.

And ig you clean/archive those logs, you can do the same for Lev1\Web\Logs

Quartz | Level 8
I can't thank you enough! We are finally back on track.
Amethyst | Level 16

Great! Very glad to read the good news! 🙂



Calcite | Level 5

We are facing similar issue on SAS Studio on SAS 9.4 M3. For each JS, CSS, PNG etc file have TTFB (Time to First Byte)//Wait time around two seconds. SAS Studio take abotu 8 minutes to load when the cache is cleared. Can you please post the steop you have taken that resolved the issue?


Adding a new problem to an old post isn't a good idea. For starters you are not even using the same software. Creating a new post will give you much better visibility and you can always reference an old post with a link if you think it will be helpful.

Calcite | Level 5

Point taken. I have opened new post.


Don't miss out on SAS Innovate - Register now for the FREE Livestream!

Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.


Register now!

Tips for filtering data sources in SAS Visual Analytics

See how to use one filter for multiple data sources by mapping your data from SAS’ Alexandria McCall.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 30 replies
  • 7 in conversation