NSX manager UI intermittently fails to load due to connectivity issues with the Security Services Platform (SSP) deployment
search cancel

NSX manager UI intermittently fails to load due to connectivity issues with the Security Services Platform (SSP) deployment

book

Article ID: 446372

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • The NSX Manager UI fails to load intermittently, specifically on the System > System Overview and System > Appliances pages.

  • The NSX cluster is up and stable in the environment
  • The NSX Cluster status shows as stable and UP, but management pages do not display data.
  • Security Services Platform (SSP) is deployed and integrated with the NSX environment
  • From the /var/log/proton/nsxapi.log, we can see that the Kafka poll shows empty results, and no messages were received from SSP
    2026-06-16T18:58:55.290Z  INFO http-nio-127.0.0.1-7440-exec-121 CommonAgentLicenseUsageServiceKafkaImpl 250989 INTELLIGENCE [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-####-####-####-############" subcomp="manager" username="#########"] Received 0 events from kafka license_usage topic
    2026-06-16T18:58:55.290Z  INFO http-nio-127.0.0.1-7440-exec-121 CommonAgentLicenseUsageServiceKafkaImpl 250989 INTELLIGENCE [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-####-####-####-############" subcomp="manager" username="#########"] Did not get any message from NAPP. Reinitialize kafka client connection
    2026-06-16T18:58:55.291Z  INFO http-nio-127.0.0.1-7440-exec-87 CommonAgentLicenseUsageServiceKafkaImpl 250989 INTELLIGENCE [nsx@6876 comp="nsx-manager" level="INFO" reqId="########-####-####-####-############" subcomp="manager" username="#########"] Destroyed license usage kafka consumer
  • In the /var/log/proton/proton-tomcat-wrapper.log file, HTTP threads are blocked on CommonAgentLicenseUsageServiceKafkaImpl.destroyConnection
  • You see the following error in the /var/log/proton/proton-tomcat-wrapper.log file
    INFO   | jvm 1    | 2026/06/16 18:54:59 | "http-nio-127.0.0.1-7440-exec-191" #12234 daemon prio=5 os_prio=0 cpu=31058.84ms elapsed=235585.27s tid=0x0000784166e46520 nid=0x28f43b waiting for monitor entry  [0x0000783c1d1e9000]
    INFO   | jvm 1    | 2026/06/16 18:54:59 |    java.lang.Thread.State: BLOCKED (on object monitor)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.proton.commonagent.license.service.CommonAgentLicenseUsageServiceKafkaImpl.destroyConnection(CommonAgentLicenseUsageServiceKafkaImpl.java:119)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       - waiting to lock <0x0000783d68c73de8> (a com.vmware.nsx.management.proton.commonagent.license.service.CommonAgentLicenseUsageServiceKafkaImpl)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.proton.commonagent.license.service.CommonAgentLicenseUsageServiceKafkaImpl.nextLicenseUsageReport(CommonAgentLicenseUsageServiceKafkaImpl.java:198)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.proton.commonagent.license.service.CommonAgentLicenseUsageServiceKafkaImpl.getReport(CommonAgentLicenseUsageServiceKafkaImpl.java:147)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.proton.commonagent.license.service.CommonAgentLicenseUsageProxy.isFeatureEnabled(CommonAgentLicenseUsageProxy.java:94)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.proton.commonagent.license.service.CommonAgentLicenseUsageProxy.getLicenseUsageCounts(CommonAgentLicenseUsageProxy.java:106)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.proton.commonagent.license.service.CommonAgentAnomalyDetectionLicenseUsageProvider.getUsageInfo(CommonAgentAnomalyDetectionLicenseUsageProvider.java:42)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.licensing.service.impl.LicensingServiceImpl.getUsageReport(LicensingServiceImpl.java:751)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.licensing.facade.LicensingFacadeImpl.getLicenseUsageReport_aroundBody20(LicensingFacadeImpl.java:331)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.licensing.facade.LicensingFacadeImpl$AjcClosure21.run(LicensingFacadeImpl.java:1)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.container.application.FacadeInterceptorHelperImpl.proceed(FacadeInterceptorHelperImpl.java:172)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.container.application.FacadeInterceptorHelperImpl.proceed(FacadeInterceptorHelperImpl.java:430)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.common.api.FacadeInterceptorAspect.annotatedMethod(FacadeInterceptorAspect.java:80)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsx.management.licensing.facade.LicensingFacadeImpl.getLicenseUsageReport(LicensingFacadeImpl.java:331)
    INFO   | jvm 1    | 2026/06/16 18:54:59 |       at com.vmware.nsxapi.license.controller.LicenseController.getLicenseUsageReport(LicenseController.java:260)
      •  
  • As per the proton-tomcat-wrapper logs, 196 out of 200 HTTP threads are blocked on CommonAgentLicenseUsageServiceKafkaImpl.destroyConnection
    zgrep 'http-nio-127.0.0.1-7440-exec' /var/log/proton/proton-tomcat-wrapper.* | grep '2026/06/16 1' | wc -l
    200

    zgrep -A1 'http-nio-127.0.0.1-7440-exec' /var/log/proton/proton-tomcat-wrapper.* | grep '2026/06/16 1' | grep BLOCKED | wc -l
    196

Environment

VMware NSX
VMware NSX 4.2.3.1

Cause

When the SSP/NAPP deployment is unavailable or disconnected, the NSX Manager receives no license usage events from the Kafka license_usage. Empty Kafka polls repeatedly trigger Kafka client reinitialization, causing HTTP threads servicing the licensing API to block until the Tomcat thread pool is exhausted, resulting in intermittent NSX Manager UI unresponsiveness.

Resolution

This issue occurs only when the SSP is down. To resolve it, ensure that the underlying SSP/NAPP deployment is healthy.

  • Check the health of the SSP deployment and ensure all required pods and services are running as expected.

  • If the SSP installation failed or is in a partial state, you must fix the deployment issues.

  • The alarm clears automatically once the NSX Manager successfully establishes a connection to the NAPP/SSP cluster.


Additional Information

Collect HAR files to troubleshoot NSX UI issues

Note: If the issue persists, collect the SSP Support Bundle and raise a support ticket with the ANS support team for further assistance, and upload the support bundle to the ticket.

Handling Log Bundles for offline review with Broadcom support.

Powered by Wolken Software