Ask the Community
Groups
Troubleshooting: Identify Traverse component causing high CPU usage - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>QUESTION:</strong><br>How do I identify the Traverse component that is constantly running very high CPU?</p> <p> </p> <p><strong>RESOLUTION:</strong></p> <p>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)</p> <p> if the process is java.exe, please provide the output of the netstat command as described in <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.zendesk.com%2Fentries%2F101058386-Troubleshooting-Collecting-Data-for-troubleshooting">https://kaseya.zendesk.com/entries/101058386-Troubleshooting-Collecting-Data-for-troubleshooting</a></p> <p>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,</p> <p>TCP [::]:7697 [::]:0 LISTENING 9832</p> <p> The process in question is listening on port 7697.</p> <p> </p> <p>Typical process mappings are as:<br>7691 - web application<br>7692 - Data Gathering Engine<br>7693 - Message Handler<br>7696 - Correlation and Summary Engine<br>7697 - activemq (jms) messaging bus</p> <p> </p> <p><em>Additional Information:</em></p> <p>These are identified in the .lax files in <TRAVERSE_HOME>\bin\*.lax (on Windows) or the <TRAVERSE_HOME>/etc/*.init (on Linux), one sees: the the file jms.lax has the entry:</p> <p>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</p> <p>The item to note here is Dcom.sun.management.jmxremote.port=7697 </p> <p> </p> <p><strong>APPLIES TO:</strong></p> <p>All versions of Traverse </p> <p> </p> <p><strong>REFERENCE:</strong></p> <p>None</p> </article> </main>