Follow

Troubleshooting: Identify Traverse component causing high CPU usage

Issue:
Identify the Traverse component that is constantly running very high CPU

Solution:

Launch Windows task manager and note the process name and process id causing high CPU usage. It may be necessary to select the 'PID (Process Identifier)' and 'Command Line' columns from View --> Select Columns. (See attachment)

 if the process is java.exe, please provide the output of the netstat command as described in https://kaseya.zendesk.com/entries/101058386-Troubleshooting-Collecting-Data-for-troubleshooting

With the netstat output,  determine the port(s) the process is listening on which in turn would tell us what component it is. Look for an entry similar to,

TCP [::]:7697 [::]:0 LISTENING 9832

 The process in question is listening on port 7697.

 

Typical process mappings are as:
7691 - web application
7692 - Data Gathering Engine
7693 - Message Handler
7696 - Correlation and Summary Engine
7697 - activemq (jms) messaging bus

 

Additional Information:

These are identified in the .lax files in <TRAVERSE_HOME>\bin\*.lax (on Wondows) or the <TRAVERSE_HOME>/etc/*.init (on Linux), one sees: the the file jms.lax has the entry:

lax.nl.java.option.additional=-Xmx512m -Xss256k -Djava.ext.dirs="C:\Program Files (x86)\Traverse\apps\activemq\lib;C:\Program Files (x86)\Traverse\apps\jre\lib\ext;C:\Program Files (x86)\Traverse\webapp\WEB-INF\lib" -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=7697 -Dcom.sun.management.jmxremote.ssl=false -Dderby.storage.fileSyncTransactionLog=true -Dorg.apache.activemq.UseDedicatedTaskRunner=false

 The item to note here is Dcom.sun.management.jmxremote.port=7697 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.