Smarts SAM: Notification processing delays seen in environment using large numbers of Java STICKY subscriptions

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Delays seen in notifications reaching the Smarts SAM console

Large numbers of STICKY subscriptions similar to the following are being used in Java code for the Smarts SAM environment:

DX_EventChoice choice = new DX_EventChoice(".*", ".*", ".*", MR_Choice.STICKY "   DX_EventChoice.ALL);

Environment

VMware Smart Assurance - SMARTS

Cause

Large numbers of STICKY subscriptions used in the Java code can cause significant delays in Smarts SAM notification processing. Unlike regular subscriptions, sticky subscriptions are not deleted once the subscribed object is removed from SAM, and will be checked against all new objects created. The process of checking each new object, such as each notification, against large volumes of STICKY subscriptions can severely impact Smarts SAM overall application performance.

Resolution

Ensure that STICKY subscriptions are being used appropriately for your environment. For example, a STICKY subscription is usually appropriate for use on a notification list subscription, but not on a notification object itself.