EditAttachPrintable
TWiki > Deployment Web > WebPreferences > AttemptingToUseRTCOnWindowsOperatingSystemLeadsIntoNativeOutOfMemory
Revision 1 - 2015-02-06 - 11:44:08 - NatarajanThirumeni

Topic title (use a lowercase style, which is known as "sentence-style" capitalization) todo.png

Authors: TWikiUser, TWikiUser
Build basis: Products, editions, or versions that apply to the content. If no build basis applies to this content, set the build basis to None.

Attempting To use RTC (Rational Team Concert) On Windows 2008 R2 Operating System Leads into NativeOutOfMemory (NOOM).

As a Jazz Admin you have got two solution to this problem.

There are two solution to this problem. Let us discuss one by one. Whatever is convenient to be implemented please test before going into production server.

Solution 1

1. To use compressedrefs to no-xcompressedrefs. According to Java team when you use no-xcompressedrefs you should be doubling current JVM heap allocation. The reasons is that when you switch to -Xnocompressedrefs option, it does disable compressed references, therefore we need to provided enough JVM memory. Please note, only 64-bit JVMs recognize these options.

JVM heap allocation sample commands

From -Xmx8g -Xms8g -Xmn2g Xcompressedrefs

To -Xmx16g <<=== double JVM maximum -Xms16g <<=== double JVM minimum -Xmn4g <<=== double JVM nursery Xnocompressedrefs <<==== removes compressedrefs to nocompressedrefs

These changes require a server restart.

You need to ensure there is enough amount of physical RAM available on the system to be use 16 gb of JVM memory. For example to use 16 gb of JVM memory, you need at least 32 GB of RAM available on the machine.

Solution 2

2. Lets go over option number 2. After lots of discussion with Java team, there is an undocumented option in the JVM which allows memory under 4GB to be reserved for later use. As a javacore shows that 500MB of low memory is being used when an NOOM (Native Out of Memory) occurs, we suggest that we start with a value of double that (1GB) to see if that fixes the problem. If NOOMs do occur with this setting, then the value can be revised upwards.

The procedure is revert all memory allocations (such as -Xmx) to half their current value. Remove -Xnocompressedrefs and replace with -Xcompressedrefs and then to add -Xgc:suballocatorInitialSize=1g

Please see a sample command over here.

From -Xmx8g -Xms8g -Xmn2g -Xcompressedrefs

to -Xmx8g -Xms8g -Xmn2g -Xcompressedrefs -Xgc:suballocatorInitialSize=1g <<=== JVM which allows memory under 4GB increased to 1GB

These changes require a server restart.

Please note, from a technical point there is no problem with -Xnocompressedrefs. If wish to use "-Xcompressedrefs" please adapt solution number #2 as Java team concluded this would be way go as there won't any fixes from the code side.

Should you have any issues or concerns open a PMR request then we can help you.

Related topics: Deployment web home, Deployment web home

External links:
http://www-01.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/com.ibm.java.doc.60_26/vm626/J9/VM/xcompressedrefs.html

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r18 | r4 < r3 < r2 < r1 | More topic actions...
This site is powered by the TWiki collaboration platformCopyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.