After applying the CSP-102547 patch on vIDM, the Horizon and OpenSearch services failed to start

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The  CSP-102547 patch is applied successfully on VMware Identity Manager, but the Horizon and OpenSearch services is not running.
  
  
• The VMware Identity Manager appliance becomes inaccessible via the web UI.
  
  
• The /opt/vmware/horizon/workspace/logs/horizon.log reports below 
  

  Caused by: java.lang.NoClassDefFoundError: javax/xml/soap/SOAPException
  at com.vmware.horizon.provisioning.adapters.mozy.MozyProvisioningAdapter.<init>(MozyProvisioningAdapter.java:60)
  at ...BundleDeploymentRuntime.deployBundle(BundleDeploymentRuntime.java:103)
  at ...ProvisioningBundleServiceImpl.initCacheDir(ProvisioningBundleServiceImpl.java:442)

• OpenSearch startup script hangs for 800 seconds and eventually fails because the /SAAS context never becomes active.

Environment

VMware Identity Manager 3.3.x

Cause

The CSP-102547 patch upgrades the vIDM Java Runtime Environment (JRE) from Java 8 to Java 11.
Java 11 removed several libraries that were previously included, including javax.xml.soap.SOAPException.

Legacy provisioning bundles (such as Mozy, AirWatch, or Google Apps) present in the vIDM database attempt to initialize during boot.
These adapters rely on an isolated classloader (Plexus ClassWorlds) that cannot see the required SOAP libraries even if they exist in the standard webapp directory.
This triggers a NoClassDefFoundError, crashing the SAAS context and preventing OpenSearch from launching.

Resolution

To resolve this issue after applying the CSP-102547 patch on vIDM, an update to the vIDM configuration file is required.
Please contact Broadcom Support for guidance on the specific configuration changes.