Monitoring and Managing a TIBCO BusinessEvents Cluster : Working with Cluster Explorer

Working with Cluster Explorer
You can do any of the following:
To Purge Inactive Unpredefined Processes
To purge, click the Purge icon. The Cluster Explorer view is cleaned. For configuration related to the purge feature see Chapter 7, MM Metrics and Features Configuration.
To View Monitored Objects
To view the Monitored Objects details, select the Monitored Objects node from the Cluster Explorer. The Cache Overview page is displayed in the right pane.
The details of various processes are displayed. For example, name of the entity, count, gets, puts, and so on.
To Execute a Method
For a table listing all the available methods, see MM Method Reference.
1.
2.
Click the Execute icon.
3.
Generating Thread Analyzer Reports
Thread analyzer connects to hosts through JMX ports and collects the thread dump for each host. Thread Analyzer analyzes the thread dump to provide information such as the following:
Thread dump compression  Threads with same stack trace are compressed into one to provide a compressed thread dump report.
Deadlock analysis  A resource allocation graph identifies the deadlocks in each of the thread dumps. (Thread analyzer creates a wait-for graph for a given set of stack traces and analyzes the graph to identify "Circular Wait Conditions" (CWC)).
Thread Dump Summarization  Provides a detailed call flow summarization of the thread dump.
The name of the report uses the format: IPAddress_Port_x.y.log. The y element is the number of the file, 0-9. You can generate up to ten log files for each set of reports for a machine, and the default size of each file is 10MB.
The x element is used if you stop and start again. It is a number used to distinguish each set of reports, when multiple sets of reports are generated for the same host.
To Generate Thread Analyzer Reports
1.
2.
Click the ThrDump icon.
3.
Host name and IP  Displays the name and address of the machine whose thread dump you want to get and analyze. (Thread Analyzer is always started on the server. Only a remote JMX connection is established with this host to obtain the thread dump). When not provided, it is assumed the host is localhost. MM connects to the JMX port configured in the site topology file.
Username and password  Enter the credentials (if any are required) used to connect to the JMX server running on the target machine. Note that these are not the JMX credentials and not those used to log into the machine.
Report Directory  Specify where on the MM server to save the Thread Analyzer report. If blank or incorrect, the thread report is saved here by default: BE_HOME/mm/logs/thread-analyzer/.
Time Interval: The interval in seconds between thread dumps. For example, if you enter 10, a thread dump is obtained every 10 seconds.
4.