Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: How to increase the Jboss XMX and XMS values in Windows Server 2008 (329970)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 8150Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This article explains how to increase or decrease the Jboss XMX and XMS values to improve performance of Smarts NCM in a Microsoft Windows 2008 Server environment.

Out Of Memory errors seen in Smarts NCM logs.

Performance issues seen in Smarts NCM.

Cause

Smarts NCM environment may show signs that there is a need to increase the Jboss XMX and XMS values to increase performance. These signs may come in the form of errors in the logs such as Out Of Memory.

Resolution

To change the values of the XMX and XMS settings in Windows Server 2008, do the following:

Note: The maximum value for XMS and XMX in Microsoft Windows is 1400M (1.4GB)

In Windows, select Start > Run.

In the Run dialog, enter regedit and click OK to launch the Registry Editor.

Browse to the following location in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NCM_Jboss\Parameters

In the right pane, double click JVM Option Number 2

Change the -Xms1024M value to what you require.

Click OK.

In the right pane, double click JVM Option Number 3

Change the -Xmx1024M value to what you require.

Click OK.

You can now exit the Registry Editor.

Restart NCM services:

[Product directory]\bin directory\ncmmaster.pl restart

Related Information

The -Xmx argument defines the max memory size that the heap can reach for the JVM.

The -Xms argument sets the initial heap memory size for the JVM. This means that when you start your program the JVM will allocate this amount of memory instantly.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant