Loading...
Loading...
The Workspace ONE team has identified that several updates to the Workspace ONE UEM AWCM Explicit Clustering configurations may cause performance degradation. These changes were introduced in Workspace ONE UEM 21.11 GA with the intent to improve performance within the AWCM Explicit Clustering solution but have shown to cause complications at scale. Note: SaaS environments and On-Premises environments that are utilizing Implicit Clustering are not affected by this configuration change.
If you are using AWCM Explicit Clustering, this configuration update has a potential to cause performance degradation. The impact of this degradation manifests as an exhaustion of CPU resources causing unexpected spikes and intermittent unresponsiveness of the AWCM service as well as AWCM pages (Statistics/Status). To confirm your environment may be impacted please verify you are utilizing Explicit Clustering. This can be viewed at the AWCM Statistics page (Ex: Https://awcm.customer.com/awcm/statistics). Once Explicit clustering is confirmed as implemented, navigate to the following location on the AWCM local host machine and check: C:\AirWatch\AirWatch\{version}\AWCM\config\AJSWrapper.exe.parameters for the following parameters:JVM_ARG=--add-modules=java.se JVM_ARG=--add-exports=java.base/jdk.internal.ref=ALL-UNNAMED JVM_ARG=--add-opens=java.base/java.lang=ALL-UNNAMED JVM_ARG=--add-opens=java.base/java.nio=ALL-UNNAMED JVM_ARG=--add-opens=java.base/sun.nio.ch=ALL-UNNAMED JVM_ARG=--add-opens=java.management/sun.management=ALL-UNNAMED JVM_ARG=--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED If you confirm the aforementioned properties are present in the parameter configuration file please follow the workaround steps below.
This will be resolved in an upcoming version of Workspace ONE UEM. Please subscribe to this KB for updates as we progress on resolution of this KB. Shared and Dedicated SaaS: No Action Required.
Short-term mitigation on on-premises environments: 1. Stop AirWatch Cloud Messaging Service on Windows 2. Go to AWCM config directory. Eg: C:\AirWatch\AirWatch\{version}\AWCM\config 3. Edit AJSWrapper.exe.parameters and remove following properties: JVM_ARG=--add-modules=java.se JVM_ARG=--add-exports=java.base/jdk.internal.ref=ALL-UNNAMED JVM_ARG=--add-opens=java.base/java.lang=ALL-UNNAMED JVM_ARG=--add-opens=java.base/java.nio=ALL-UNNAMED JVM_ARG=--add-opens=java.base/sun.nio.ch=ALL-UNNAMED JVM_ARG=--add-opens=java.management/sun.management=ALL-UNNAMED JVM_ARG=--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED 4. Save AJSWrapper.exe.parameters. 5. Start AirWatch Cloud Messaging Service.
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.