After you have successfully enabled JMeter deep diagnostics (see Section, “JMeter”), you are now ready to run. RTI provides deep diagnostics when you run your JMeter tests as usual, from prepared scripts or interactively.
In this example we have a JMeter script running in the JMeter GUI on our local Windows workstation, exercising our ecommerce application in JBoss on a remote Linux server: Both JMeter and JBoss have been enabled for RTI data collection.
We start the RTI console and verify that we are connected to the host or hosts where the test is running. In this case we can see that RTI is collecting data in both the jmeter and jboss_ecommerce collectors:
After exercising our application we can transfer the RTI data from the remote host to the RTI console to analyze our application performance. To do this we select the Transfer Deep-Dive Performance Data link on the welcome page:
This displays the Get Data From Collectors dialog where we will specify which data to get:
In this case we have selected to transfer data from both the jmeter collector on localhost which started the transactions, and the jboss_ecommerce collector on our remote host where they were processed. We keep the default name for the name of the local data set to hold the data, choose to get the last 10 minutes of data, and choose to ignore methods less than 5 milliseconds long to filter out near-zero-duration methods.
Once the data is downloaded to the RTI console it is correlated and an overview of the data is displayed:
The columns and sort orders shown are the default when starting on a new machine. The chart on the lower right shows that all the transactions collected initiated with JMeter (in red) and were fairly consistent over time. The JMeter events are sorted by Create Time, so the first thing one can do to highlight long-running transactions is to sort by descending Elapsed Time:
Now we see these JMeter events indicate that they can be expanded to show multiple events that comprise these transactions. We can see times around ten seconds -- let's see what's taking all that time. Just double-click on a line to "Focus On" the transaction, which replaces this view with the fully expanded decomposition of the transaction. In this case there are a lot of events underneath, so you can click on the "expand view" decoration in the upper right. Then you can sort by the Percent column to show the "Slowest Path" in red:
The events at the end of each path are where to look: click on the Transaction Properties tab in the lower left, to learn more about each Event. As an exercise, find the SQL property for the Hibernate-QueryList event.

loading table of contents...