OPERATIONAL DEFECT DATABASE
...
...
You see the following in the broker's tomcat logs the installation is corrupted and we need to re-install the broker, 2018-08-02T13:47:46.041-04:00 DEBUG (11F4-10DC) <console-redirection> [ws_TomcatService] STDOUT: 02-Aug-2018 13:47:46.041 INFO [JMS Thumbprint Manager] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [com.vmware.vdi.messagesecurity.Identity]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access. java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [com.vmware.vdi.messagesecurity.Identity]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access. When logging into the Horizon admin page you see the error "java.lang.NoClassDefFoundError: Could not initialize class com.vmware.vdi.admin.be.VCManager"
This is a known issue.Horizon 2012 (8.1) and later contain a coded fix for this.
To work around this issue: (in a scenario where a replacement o/s is not feasible) Remove the broker from the cluster using vdmadmin.Uninstall the connection server.Delete all directories of brokers and make sure no broker binaries are available.Install broker again as a replica.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
