The following exceptions are observed in Usage Meter logs.
dss_main.log:
c.v.um.common.platform.JournalClient with Socket Timeout Exception:
YYYY-MM-DD 09:32:15.061 ERROR --- [pool-2-thread-1] c.v.um.common.platform.JournalClient : Read timed out
java.net.SocketTimeoutException: Read timed out
at java.base/sun.nio.ch.NioSocketImpl.timedRead(Unknown Source)
vmware-um-journal.log:
The following OutOfMemoryError is outputed periodically:
Mon Day 08:40:46 ck2tky4-vvopum11 start-journal-service.sh[1634]: YYYY-MM-DDT08:40:46.573Z ERROR 1634 --- [VCF
Usage Meter Journal Service] [0.1-8051-exec-4] 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
Mon Day 08:40:46 ck2tky4-vvopum11 start-journal-service.sh[1634]: java.lang.OutOfMemoryError: Java heap space
VMware Usage Meter 9.0.x
Due to a large number of journal notification messages that are accumulated, Journal Service in Usage Meter detects lack of Java heap memory as exception and it also generates exception at JournalClient, finally stops to load consumption data.
# vi /opt/vmware/cloudusagemetering/platform/bin/start-journal-service.sh
export MAX_MEMORY="512M"
start.sh All -r