Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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 SAM 9.1: OI-Notif stops processing traps without warning, logging or alerting (372901)

Last Updated: 9/4/2023Categories: TroubleshootingTotal Views: 4301Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Smarts Service Assurance Manager (Smarts SAM) OI-Notif stops processing traps without warning, logging or alerting

Cause

From the Smarts SAM OI log file we can see that there is an "out of memory" error reported for the Java heap size for the eciProcessors thread as well as the "EventPoller on notifPublicationQueue" thread:

[April 13, 2013 9:43:08 AM GMT+00:00 +102ms] t@1127627072 platform

MAIN_MSG-*-STDFD_ERR-stderr: Exception in thread "eciProcessors:processor_1" java.lang.OutOfMemoryError: Java heap space

[April 13, 2013 9:47:16 AM GMT+00:00 +735ms] t@1127627072 platform

MAIN_MSG-*-STDFD_ERR-stderr: Exception in thread "EventPoller on notifPublicationQueue" java.lang.OutOfMemoryError: Java heap space

java.lang.OutOfMemoryError: Java heap space

Resolution

If you encounter this issue, there are few settings and parameters in Notif that can be tuned to improve the performance of trap processing:

JVM Memory Size

Notif ECI Worker Threads size

NotifEventQueue Size limit

The following sections explain how to adjust each of these Notif settings and parameters.

JVM Memory Size
There are two jvm parameters (-DXmx and -DXms) which define the maximum and minimum committed memory size for the jvm process during startup. The default values are 1024MB and 128MB respectively. These values can be increased based on the system needs.

How to change values:

1. The following asl files needs to be modified with new values.

SAM/smarts/rules/ics/Notif-init.asl

SAM/smarts/rules/icoi/Notif-init.asl

2. Add the following lines in asl files, in INIT_JVM rule

jvm->add_prop("-Xms3072m"); //3GB min commit size. Make sure 3GB free RAM space before starting

jvm->add_prop("-Xmx4096m"); //4 GB max value.

3. Restart the OI server

Notif ECI Worker Threads size
This setting defines the number of worker threads that will consume events from the NotifEventQueue. The default value of this is 4. As the number of events pile up in the queue, the memory size will increase, increasing the threads will consume those events from queue and can prevent memory growth.

How to change values:

1. Edit the following import file (local/conf/icoi/Notif_Settings.import)as shown below:

Notif_Settings::Notif-Settings

{

Active=TRUE

PendingUpdate=FALSE

LogSize=8388608

NbrLogFiles=5

LogLevel=2

MaxEnumWildcard=4

ProcessCount=4 // Defines the thread size; Increase this value to suitable value based on the number of processors.

}

2. Restart the OI server

NotifEventQueue Size limit
This setting defines the max events that can be present in the queue. The events exceeding this limit will be discarded. Currently there is neither logging nor any notifications being generated when events are discarded due to the QueueSize limit. By default, this queue is unbounded and set to maximum.

How to change value:

1. Add the following line to the Notif_Settings.import file (local/conf/icoi/Notif_Settings.import) as shown below:

call notifInterface::notifEventQueue setMaxSize 50000

2. Restart the OI server.

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 - SMARTS

Take Our Survey

Support Assistant