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 SAM: What are "Sticky" Subscriptions? How do we identify Sticky Subscriptions and where they come from? (305457)

Last Updated: 11/9/2022Categories: How toTotal Views: 15978Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

This article explains the purpose and function of Sticky Subscriptions used in Smarts SAM, including how to identify Sticky Subscriptions and the source of those subscriptions.

Sticky Subscriptions are a method used in Smarts SAM to make the Smarts SAM server remember the client-s subscription pattern, so that the server may try to match the client-s pattern against newly created repository instances (after the subscription was done), in addition to the repository instances that existed at the time of subscription.

How Sticky Subscriptions work
Sticky Subscriptions function like pattern matching with wildcard entries. A Sticky Subscription matches certain patterns while a Smarts SAM client is subscribing to the Smarts SAM server. The Smarts SAM server will keep remembering this pattern even if new instances are created,  and will attempt to apply and match the pattern before sending the information to the client. Sticky Subscriptions can be applied for anything and everything for which a Smarts SAM client can subscribe, such as Topology elements, attributes, notifications and so on. For example, if you subscribe for certain attributes and use the sticky option, this will indicate to the server while processing the subscription to try to match everything in the pattern.

Precaution when using Sticky Subscriptions
If large numbers of Sticky Subscriptions are used in the Java code, it 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 and memory footprint. So, we suggest to avoid such subscription.

How to identify a subscription is "sticky"
You can see whether a subscription is sticky in the Smarts SAM server logs. Sticky Subscriptions will have "STICKY" associated with them. In the following example, you can see that the external Java client is subscribing with the STICKY option:

[January 22, 2014 3:05:12 AM GMT +222ms] t@1******* SM_ProtocolEngine-123456 unknown Java
-Subscription change: propertyUnsubscribeAll    client: SM_SocketObserver-123456 unknown Java choice: ICS_Notification::NOTIFICATION-NetworkAdapterRedundancyGroup_NARG-1234__/port=****_BondedPortAggregateLow::Active|IsRoot::[STICKY]

How to identify the source (client) of Sticky Subscriptions
To identify the client using a Sticky Subscription, do the following:

Take the client ID from the server logs. In the above example, the client ID is 123456.

Match the client ID in the sm_monitor logs, and identify the IP address of the client that is making the request. This will get the following:

Id      User   Privs  Host  PID              Since                        Description          Client Version
12345    user    ALL   000  unknown   January 19, 2014 4:54:32 AM GMT        Java                  unknown

Verify in the external Java code how the choice subscription is done from the code. You might have code for DX_EventChoice or some other class might have the parameter passed with STICKY option.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

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