NSX manager stuck as no timeout present in SSO client library

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:

• NSX manager goes unresponsive.
• SSO registration or configuration throws Null Pointer exception.

GMT ERROR http-nio-127.0.0.1-7441-exec-2 VcConnection:445 - SSO timeout for user : [email protected].
java.util.concurrent.TimeoutException
 at java.util.concurrent.FutureTask.get(Unknown Source)
 at com.vmware.vshield.vsm.vcserver.VcConnection.getSamlToken(VcConnection.java:441)
 at com.vmware.vshield.vsm.vcserver.VcConnection.loginUsingSAMLToken(VcConnection.java:338)
 at com.vmware.vshield.vsm.sso.utils.tasks.DefaultSSOClientKeepAliveThread.authenticateUsingSamlToken(DefaultSSOClientKeepAliveThread.java:157)
 at com.vmware.vshield.vsm.sso.utils.tasks.DefaultSSOClientKeepAliveThread.testSSOClientConnection(DefaultSSOClientKeepAliveThread.java:122)
 at com.vmware.vshield.vsm.sso.facade.impl.SSOConfigFacadeImpl.getLookupServiceStatus(SSOConfigFacadeImpl.java:114)
 at com.vmware.vshield.vsm.sso.restcontroller.SSOConfigController.getLookupServiceStatus_aroundBody6(SSOConfigController.java:58)
 at com.vmware.vshield.vsm.sso.restcontroller.SSOConfigController$AjcClosure7.run(SSOConfigController.java:1)
 at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:221)
 at com.vmware.vshield.vsm.aspects.web.RequestBodyValidatorAspect.aroundController(RequestBodyValidatorAspect.java:49)
 at com.vmware.vshield.vsm.sso.restcontroller.SSOConfigController.getLookupServiceStatus(SSOConfigController.java:56)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:176)........
...........

Environment

VMware NSX for vSphere 6.2.x
VMware NSX for vSphere 6.3.x

Resolution

This issue has been resolved in NSX 6.2.9, NSX 6.3.4 and NSX 6.4.0.

Workaround:
To workaround this issue, restart NSX manager.