Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SMA does not persist node definitions after IE cache clear

SA-10521

Summary



System Management Application (SMA) does not persist node definition, that is, some users are able to access the full list, some see only a partial list and others see no nodes at all.

Behavior changes as the individual users clear their browser cache and refresh the SMA landing page.


Error Messages



Not Applicable

Steps to Reproduce



1. Access SMA landing page and observe the list of nodes.
2. A refresh of the landing page or clearing of cache may impact the available nodes upon the next visit to the SMA landing page.


Root Cause



The root cause of this problem is defect or misconfiguration in the operating environment. SMA is deployed on the cluster, which means that JVM that serving up prsysmgmt application cannot be different for new browser or session requests. Every JVM stores its own copy of nodes.xml that can have different PRPC node configuration and hence the end user will see inconsistent SMA node configuration for subsequent requests.

Resolution



This issue is resolved by making the following change to the operating environment:

​Deploy SMA on a standalone (separate JVM) and not on the cluster for ease of maintenance and consistency.

Published February 29, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us