UIM performance very slow or no groups display after upgrade
search cancel

UIM performance very slow or no groups display after upgrade

book

Article ID: 269044

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

UIM performance is very slow after upgrade to DX UIM 20.4 CU6. The page takes too much time to load. Groups (group members) do not populate within a reasonable time or no groups show at all. This may also affect Inventory display.

Environment

  • Release: 20.4 CU6 or higher
  • wasp

Cause

  • wasp errors:
ERROR [Thread-67, com.nimsoft.nimbus.NimProbeBase] Error when running on timer method in separate thread. Reason is (1) error, Not able to callback for timer cbHeartbeatOnTimer.60000. Reason is java.lang.OutOfMemoryError: GC overhead limit exceeded
ERROR [https-jsse-nio-443-exec-153, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/uimapi].[rest]] invoke() Servlet.service() for servlet [rest] in context with path [/uimapi] threw exception

Resolution

  • nas: housekeeping related to nas retention settings were not completing due to time outs.  These large tables were affecting the performance of the database responses and impacting OC.  These tables were pruned and retention settings were decreased to allow for the large environment and high alarm count.

nas Best Practices, Tips and Techniques (for Large Environments)

  • wasp: Also due to OutOfMemory errors in the wasp.log's, one example log extract is shown below...

Please do the following for EACH UMP / Operator Console instance:

1. Via Raw Configure mode, under startup->options, please add an additional 2GB to each WASP instances' current java min/max settings...for example:

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=jrSCP0NMTDVy5SWasdF8zg==

2. Deactivate the wasp

3. Wait for the port and PID to diappear

4. Activate wasp

Additional Information

You can also review the wasp log at loglevel 5 to see how much memory is still available and if its close the maximum memory already configured/allocated add 1-2 GB more to the java heap settings.