CLM and memory allocation
Accepted answer
Hi Sterling,
You need to remove -Xmx4g -Xms4g from the arguments. These parameters are set in was by specifying Initial and maximum heap size. After removing these parameters and restarting WAS it should be working correctly.
Let us know if it helps for you.
Best regards,
Krzysztof Kazmierczyk
You need to remove -Xmx4g -Xms4g from the arguments. These parameters are set in was by specifying Initial and maximum heap size. After removing these parameters and restarting WAS it should be working correctly.
Let us know if it helps for you.
Best regards,
Krzysztof Kazmierczyk
5 other answers
Hi Sterling,
If you want to increase the maximum JVM heap size on a CLM application running on WebSphere, you can do it from the WebSphere admin console (ie - http://clmweb.ibm.com:9060/ibm/console). The recommendation is to set the maximum heap no higher than 1/2 the available physical memory assuming you're only running one WAS profile.
Once logged in to the WAS admin console, go to Servers -> Server Types -> WebSphere Application Servers -> <server_name> -> Java and Process Management -> Process Definition -> Java Virtual Machine -> You'll see the initial and maximum heap size there. The recommendation is to set them to the same value. Here is the documentation on JVM settings from the WebSphere 7.0 InfoCenter. Hope it helps,
If you want to increase the maximum JVM heap size on a CLM application running on WebSphere, you can do it from the WebSphere admin console (ie - http://clmweb.ibm.com:9060/ibm/console). The recommendation is to set the maximum heap no higher than 1/2 the available physical memory assuming you're only running one WAS profile.
Once logged in to the WAS admin console, go to Servers -> Server Types -> WebSphere Application Servers -> <server_name> -> Java and Process Management -> Process Definition -> Java Virtual Machine -> You'll see the initial and maximum heap size there. The recommendation is to set them to the same value. Here is the documentation on JVM settings from the WebSphere 7.0 InfoCenter. Hope it helps,
Comments
I would also have a look at:
Track recommended JVM options for running CLM servers
(Jazz Collaborative ALM, Task: 198140)
We are running 4 parallel profiles with this recommended settings with very good results.
Hi Sterling,
The issue is that your -Xmx and -Xms are set to 4G in your JVM arguments, so they're overriding the settings you've adjusted. You can either update them in the JVM arguments (change -Xmx4G -Xms4G to -Xmx8G and -Xms8G), or remove them and keep the properties you've set in the Min/Max settings on the same page. Either one will fix the issue.
The issue is that your -Xmx and -Xms are set to 4G in your JVM arguments, so they're overriding the settings you've adjusted. You can either update them in the JVM arguments (change -Xmx4G -Xms4G to -Xmx8G and -Xms8G), or remove them and keep the properties you've set in the Min/Max settings on the same page. Either one will fix the issue.
@Benjamin: I must be doing something wrong. I went into WAS and changed it to 8192...and it still shows the same after a WAS restart:
What does the Free indicate? Do I have something set wrong?
thanks
VM Memory Usage
| Maximum Memory Allocation | 4096 MB |
| Current Memory Allocation | 4096 MB |
| Free Memory | 82 % |
Hi Sterling,
Can you confirm the configuration was saved by checking the properties again after the restart? If not, you'll need to make the changes again, save the configuration when prompted, then restart WAS again.
The "Free Memory" indicates the amount of memory not in use (so a high number there is good). You can also check more specific JVM usage statistics by going to https://server:port/rm/rmadin -> Logging -> View JVM Properties (at the bottom of the page). I'm not sure the "Current Memory Allocation" in your screenshot is showing the actual allocation, but rather the minimum heap. The RM page I mentioned above shows a better breakdown of memory usage.
Can you confirm the configuration was saved by checking the properties again after the restart? If not, you'll need to make the changes again, save the configuration when prompted, then restart WAS again.
The "Free Memory" indicates the amount of memory not in use (so a high number there is good). You can also check more specific JVM usage statistics by going to https://server:port/rm/rmadin -> Logging -> View JVM Properties (at the bottom of the page). I'm not sure the "Current Memory Allocation" in your screenshot is showing the actual allocation, but rather the minimum heap. The RM page I mentioned above shows a better breakdown of memory usage.
Hello Benjamin:
|
MB |
||||||||||||||||||||||||||||||||||||||||||
|
MB Here are my arguments: -Xmx4g -Xms4g -Xmn512m -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 JVM Memory
|