How to activate/deactivate the Java Profiler for TIBCO LogLogic Security Event Manager

How to activate/deactivate the Java Profiler for TIBCO LogLogic Security Event Manager

book

Article ID: KB0077538

calendar_today

Updated On:

Products Versions
TIBCO LogLogic Security Event Manager all versions

Description

The procedure below describes how to activate the Java profiler on a LogLogic SEM host to use for identifying the root cause for out of memory situations.

Resolution

Activating the profiler
1. Open the file: /etc/init.d/exa_runtime_InstanceName
2. Edit the line "JAVA_OPTS"
Original:
JAVA_OPTS="-DinstanceType=runtime -DinstanceName=$CLIENT_NAME ..."
New:
 JAVA_OPTS="-DinstanceType=runtime -DinstanceName=$CLIENT_NAME ...  -Xrunhprof:heap=sites,file=/tmp/ExaDump.txt,depth=12,interval=10"

The new text gets added at the end of the existing JAVA_OPTS string value.
3. Save and exit the file being edited.
4. Restart the runtime: /etc/init.d/exa_runtime_InstanceName restart
5. When you see an Out Of Memory execute kill Runtime_pid

Note: Do not execute /etc/init.d/exa_runtime_InstanceName stop and do not kill the process with option "-9". 

Deactivating the profiler
1. Remove the added text to the JAVA_OPTS line from the file /etc/init.d/exa_runtime_InstanceName
2. Restart the runtime: /etc/init.d/exa_runtime_InstanceName restart

Issue/Introduction

This article explains how to activate/deactivate the Java Profiler in LogLogic SEM.
Powered by Wolken Software