Sometimes, the memory will utilize high due to watchdog service. This article explains how to identify if the watchdog service is utilizing more memory.

To identify which process is utilzing more memory, please use the below command:

[root@space-0319062021000014 ~]# ps aux --sort -rss | head

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND

jboss 5538 95.7 35.8 17220072 11594048 ? Sl 2024 133062:52 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.312.b07-1.el7_9.x86_64/jre/bin/java -D[Server:server1] -D[pcid:2134299582] -Xms10240m -Xmx10240m -server -d64 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/cache/jboss -Dsolr.solr.home=/usr/local/jboss/standalone/configuration/solr -Dsolr.data.dir=/usr/local/jboss/standalone/data/solr -Djboss.host.server.connection.timeout=90000 -Djboss.host.domain.connection.timeout=90000 -Djboss.as.management.channel.close.timeout=90000 -Djboss.as.management.blocking.timeout=90000 -Djava.util.Arrays.useLegacyMergeSort=true -Dsvnkit.http.sslProtocols=TLSv1.2,TLSv1.1,TLSv1,SSLv3 -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:/var/log/jboss/platform-gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=128K -Xss2m -XX:MetaspaceSize=2048m -XX:MaxMetaspaceSize=2048m -XX:NewSize=4096m -XX:MaxNewSize=4096m -XX:SurvivorRatio=6 -XX:TargetSurvivorRatio=90 -XX:+UseG1GC -XX:+UseStringDeduplication -Djava.ext.dirs=/usr/lib/jvm/jre/lib/ext1 -DND_COLLECTION_BATCH_SIZE=30 -DND_DEVICE_REQ_THREAD_COUNT=10 -DFIPSMode=false -Dhibernate.dialect=org.hibernate.dialect.MySQL57Dialect -Dhibernate.dialect.storage_engine=innodb -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djboss.as.management.blocking.timeout=90000 -Djboss.as.management.channel.close.timeout=90000 -Djboss.bind.address=0.0.0.0 -Djboss.cache.dir=/var/cache/jboss -Djboss.default.multicast.address=228.12.4.6 -Djboss.domain.log.dir=/var/log/jboss -Djboss.domain.master.address=jmp-CLUSTER -Djboss.home.dir=/usr/local/jboss -Djboss.host.domain.connection.timeout=300000 -Djboss.host.server.connection.timeout=300000 -Djboss.messaging.server.1=space-0319062021000004 -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.msc.max.container.threads=64 -Djgroups.bind_addr=space-0319062021000014 -Djgroups.udp.internal_thread_pool.max_threads=10 -Djgroups.udp.internal_thread_pool.min_threads=5 -Djgroups.udp.ip_ttl=15 -DnmaPort=8002 -DnmaProtocol=https -Dnode.ip=10.12.4.4 -Dnode.port=443 -Dorg.apache.catalina.session.ManagerBase.SESSION_ID_LENGTH=50 -Dorg.apache.coyote.http11.Http11Protocol.SERVER=Server -Dorg.jboss.as.web.deployment.DELETE_WORK_DIR_ONCONTEXTDESTROY=true -Dorg.jboss.as.web.sso.ClusteredSingleSignOn.maxEmptyLife=0 -Dorg.jboss.server.bootstrap.maxThreads=64 -Dsolr.data.dir=/usr/local/jboss/standalone/data/solr -Dsolr.solr.home=/usr/local/jboss/standalone/configuration/solr -Dweb.protocol=https -Djboss.server.log.dir=/var/log/jboss/servers/server1 -Djboss.server.temp.dir=/usr/local/jboss/domain/tmp/servers/server1 -Djboss.server.data.dir=/usr/local/jboss/domain/data/servers/server1 -Dlogging.configuration=file:/usr/local/jboss/domain/data/servers/server1/logging.properties -jar /usr/local/jboss/jboss-modules.jar -mp /usr/local/jboss/modules org.jboss.as.server

root 7889 12.2 27.3 9003948 8823836 ? Ss 2024 17000:00 /usr/bin/perl /usr/bin/jmp-watchdog >> /var/log/jmp-watchdog.log 2>&1

elastic+ 13177 0.2 9.3 11396488 3020860 ? Ssl 2024 345:53 /bin/java -Xms7g -Xmx7g -XX:+UseConcMarkSweepGC -

Here, root user is utilizing more memory (27.3%) due to watchdog service which is not expected.

To fix the issue, please restart the jmp-watchdog service and check if it is utilizing the memory.

If the issue persists, please contact JTAC for additional assistance.