Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

In /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log, you see messages similar to:

[YYYY-MM-DDTHH:MM:SS.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.
        at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)
        at com.sun.proxy.$Proxy159.logout(Unknown Source)
        at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logoutInternal(DefaultAuthenticationProvider.java:548)
        at com.vmware.vise.security.spring.DefaultAuthenticationProvider.access$400(DefaultAuthenticationProvider.java:84)
        at com.vmware.vise.security.spring.DefaultAuthenticationProvider$2.run(DefaultAuthenticationProvider.java:487)
        at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logout(DefaultAuthenticationProvider.java:457)
        at com.vmware.vise.security.SessionListener.handleSessionDestroyed(SessionListener.java:135)
        at com.vmware.vise.security.SessionListener.sessionDestroyed(SessionListener.java:71)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server 7.0.x
VMware vCenter Server 6.7.x

Cause

The issue is caused by the LookupService being down when the vsphere-ui starts.

Resolution

Currently, there is no resolution.

Workaround:

To workaround this issue, stop and start the vsphere-ui service.

1. Stop the vsphere-ui service by running the command:

service-control --stop vsphere-ui

2. Start the vsphere-ui service by running the command:

service-control --start vsphere-ui

Note: Existing UI logins will be closed and the users will have to re-login.