11-02-2015 06:09 PM
There is a peculiar Java(TM) Platform SE binary process that can be traced back to SAS web services that is eating up about 60% of our CPU. We have never seen this issue before. We have closed all SAS consoles and even restarted the server, but the Java application starts up again. I am primarily a programmer and not an IT expert so please be patient. Any suggestions as to what might be the problem here will be much appreciated. I will mention that we do have a SAS server setup so outside users can access SAS through Enterprise guide and the Excel plugin. I have also created some very basic reports using Stored Processes and the web application server, but this was months ago and no one is currently using it.
Thank you in advance!
11-02-2015 06:24 PM
What is your SAS version and maintenance level? There are a number of possible causes for this. If you are running SAS 9.4, the SAS Environment Manager agents can use a significant amount of CPU, particularly if they are not stopped and started in the recommended way.
11-03-2015 11:05 AM
We are running SAS 9.4. I'm not sure what the maintenance level is... can it be determined using proc setinit? The confusion that I am having is that we have never experienced this problem before so we are trying to troubleshoot so that the problem doesn't occur again in the future.
11-02-2015 06:48 PM
you can also use a tool like https://technet.microsoft.com/en-us/sysinternals/bb896653 sysinternals process explorer to find out the full command line of the java process and confirm exactly which JVM it is. (SASServer1, Environment Manager, etc)
11-03-2015 11:22 AM
Using dpage's suggestion, I can look at the command line used to generate the Java.exe. The path associated is:
If that helps at all in diognosing the problem.
11-03-2015 04:25 PM
Yea, that's SASServer1. I'd check the Lev1/Web/WebAppServer/SASServer1_1/logs/server.log to try and get a better idea of what's going on - server1 can use a great deal of resources while it's starting - but once it reaches steady state it should be fairly low CPU utilization. If for some reason it's crashing, it will constantly be restarted by tanuki and that may be what you're seeing.