Registering vCenter server to Usage Meter does not complete when clicking [PLEASE ACCEPT CERTIFICATE] button

Products

• VMware Usage Meter

Issue/Introduction

• When registering a new vCenter server to Usage meter and clicking [PLEASE ACCEPT CERTIFICATE], the status does not change from "Credentials verified" to "OK."
• There are already many vCenter and other products registered with the VCF Usage Meter.
• Performing Test Connection from Settings > Cloud Connectivity, fails with the error 504 Gateway Time-out.
• OOM (out of memory - java.lang.OutOfMemoryError) exceptions in /opt/vmware/cloudusagemetering/platform/log/vmware-um-journal.log :
  YYYY-MM-DDTHH:MM:SS.XXXZ ERROR ### --- [VCF Usage Meter Journal Service] [https-jsse-nio-127.0.0.1-####-exec-###] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Handler dispatch failed: java.lang.OutOfMemoryError: Java heap space] with root cause

Environment

VCF Usage Meter 9.x

Cause

Heap memory exhaustion of journal service occurred due to the number of metered products.

Resolution

Follow the steps below to increase the heap memory for the journal service.

1. Stop the Usage Meter appliance and take an offline (stopped) snapshot to allow for rollback in the a failure.
2. Start the appliance and log in as the root user via SSH.
3. Execute the following command to change the MAX_MEMORY value from 512M to 1536M and save it.

# vi /opt/vmware/cloudusagemetering/platform/bin/start-journal-service.sh

---------------------
#!/bin/bash

export JAVA_OPTS="-Dapp.name=journal-service"
export MAX_MEMORY="512M" (Change the value to 1536M)
export DB_INIT=$1
export DATA_SOURCE_FILE_NAME="journal-service.db"

basedir=$(dirname "${BASH_SOURCE[0]}")
. ${basedir}/prepare-service-env.sh

export APP_NAME="journal-service"
export JAVA_OPTS="${JAVA_OPTS} -Dserver.notification.conf=${app_root}/conf/notification_runners.json"
export JAVA_OPTS="${JAVA_OPTS} -Dserver.monitor.log.dir=${app_root}/log"

${app_root}/bin/journal-service ${APP_ARGS}
---------------------

4. Restart the Usage Meter appliance and verify that the corresponding vCenter is registered and the status is "OK."

Additional Information

reportFatalErorr call with errorCode 'ERR_THREAD_WATCHER' and error Message 'Issue detected for UploaderThreadsWatcher' in vCloud Usage Meter 4.8