I’ve been preparing to launch our site and in generating a CSR, which has been taking too much time, we discovered The java process running percussion is using 100% of available CPU power. I rebooted the server but it quickly returned to the same state.
Any ideas what could be causing this and how to remedy it?
First, can you share with me the specifications of your CM1 application server, i.e. is it a dedicated server, what type of processor is it running, how much RAM does the system have available, etc.?
Additionally, in your PercussionServer.lax file, which is located in the CM1 root directory, please look for a block of text that looks like this:
# Java arguments
lax.nl.java.option.additional=-Dprogram.name=RhythmyxServer.exe -Xms256m -Xmx1228m -Djava.endorsed.dirs="AppServer/lib/endorsed" -Djava.library.path=./bin -server -XX:MaxPermSize=256m -Dfile.encoding=UTF8 -Dsun.jnu.encoding=UTF8 ```
Can you share with me what both the **-Xms** and **-Xmx** properties are currently set to in your instance? Thanks!
This is a Virtual 2008 R2 server dedicated to running percussion and related services.
Single Xeon Cpu @ 1.87Ghz 3 GB RAM
lax.nl.java.option.additional=-Dprogram.name=RhythmyxServer.exe -Xms256m -Xmx1024m -Djava.endorsed.dirs=“AppServer/lib/endorsed” -Djava.library.path=./bin -server -XX:MaxPermSize=256m -Dfile.encoding=UTF8 -Dsun.jnu.encoding=UTF8
To be honest, CM1 is really going to push that system to its limit. On our Help site we list a dual core processor of at least 3GHz as the minimum https://help.percussion.com/percussion-cm1/install-setup/installing-cm1/system-requirements. Additionally, when running your server as both your application server (for CM1) and your web server, you really would be better off with at least 4GBs of RAM. Because this is a virtual server, is there any chance you would be able to allocate any additional processing power and RAM to this machine?
In the meantime, it won’t hurt to increase CM1’s JVM memory allocation to 2GB from its current 1GB. To do this, first shutdown CM1 (ensuring that all java.exe processes go down), and then, in your PercussionServer.lax file, change the line that reads -Xmx1024m to -Xmx2048m. Then, start CM1 back up and see if the performance improves any.
Thanks Nathaniel. Would this be enough?
4GB of ram, 60 GB of storage and 4,000GB bandwdith a month.
Does this package increase your processor’s power at all (i.e. additional core, more GHz, etc.)? This might be your largest bottleneck at this point.
No. CPU is still shared and stays unchanged. This package would just add more ram, bandwidth, and space.
In my current situation what is the best route for me to take? Move the web hosting to a different server? Add more RAM to the existing server?
I have to say that moving to a new server that fully meets the minimum system requirements would be your best long-term solution. It wouldn’t hurt, though, to make those JVM memory allocation changes now to see if that helps you out in the short term.
I’ve managed to upgrade our server the 4GB, Jesse our IT support here at NEEP has made the adjustments you suggested.
When I log on to the remote server and examine performance under the task manager the CPU is still 100% - with no activity on the server a part from CM1. The site is not live and I am the only person logging into CM1 and yet CPU is still maxing out 100%. Any reason for this that you can think of? Also I’m getting this message: could this have anything to do with the issues we’re facing?
Thanks for trying that. That pop-up message should not be a problem, as it just has to do with how you have allowed the Percussion service to interact with your server’s desktop (this can be easily changed). I’m going to create a support ticket so that we can look into your options here more closely; please check your inbox momentarily.
For other customers with similar issues, while we still certainly recommend that customers always meet our system requirements when running CM1, it turns out Carrie was encountering a specific issue that was causing their CM1 java.exe process to use 100% of their CPU even when no one was logged into the system. The root cause of this problem has been identified and a bug report has been filed in our internal system.
If any other customers observe this type of behavior – where the main CM1 Java process appears to be very active when no one is logged into the system – there are a few ways to diagnose if your environment is suffering from this same issue, and an easy method to correct the problem. Because the steps to diagnose and correct this issue are more advanced, please reply to this topic if you would like someone to look into this with you, and a member of support will be happy to contact you directly.
Nathaniel, Please contact me regarding a performance issue on the server. Thanks.
Hi Jerome, a support ticket has been created on your behalf. You should be receiving an email notification shortly.