Trace and Request Analyzer for WebSphere Application Server


A tool that detects delays and hangs in WebSphere trace and HTTP plug-in trace

WebSphere Application Server trace is used to obtain detailed information about running components, including application servers, clients, and other processes in the environment, such as the time and sequence of methods called by base classes.
IBM Trace and Request Analyzer for WebSphere Application Server allows you to find delays and possible hangs from WebSphere trace files and HTTP plug-in traces by parsing call trees of methods and traces and calculating delays in each method and trace.
The package includes a Java graphical user interface (GUI) application that displays delays in lists and tables.
With IBM Trace and Request Analyzer for WebSphere Application Server you get a useful tool for analyzing and identifying problems in trace files.

Here is how to use it:

You need to use the Java 2 Platform, Standard Edition version 5.0 or higher Java Runtime Environment (JRE) to run IBM Thread and Monitor Dump Analyzer for Java Technology.

Usage <Java path>java –Xmx[heapsize] –jar tra<IBM Trace and Request Analyzer version>.jar

For example,

C:\java50\bin\java –Xmx200m –jar tra10.jar

=> Starts IBM Trace and Request Analyzer for WebSphere Application Server

If there’s java.lang.OutOfMemoryError while you are processing trace files, please try increasing the maximum heap size (-Xmx) value to give the JVM more memory.

Maximum heap size should not be larger than the size of available physical memory size for this tool due to performance issue.

Steps:

Note: A detailed tutorial with screenshots is present in the zip file, you download. These are just an outline of steps.

1. Start IBM Trace and Request Analyzer for WebSphere Application Server

2. Select File-> Open WebSphere Trace or HTTP Plugin Trace

3. Select trace file(s) that you want to analyze. [If multiple files are selected, they are considered to be contiguous traces. Please do not select multiple files if they are not contiguous traces.]

4. Progress bars are shown

6. Loaded trace files are listed in the Trace List table.

7. Select a trace file to review Environment Information for the trace

8. Click on Method Duration from Analysis menu or pop up menu

9. Method level delays are displayed with sorted time.

· Trace Method Analysis : Sorted list of trace method entry/exit taken longer than threshold

· Time: Time between trace method entry and exit of same thread id

· Trace: Actual line from trace file

· Line Number: Line number of the trace entry

· File : File name

10. Click on the first entry that has xxxx ms of delay to see actual trace entries

11. Click on next row to display traces of exit point of the same method

12. By selecting Trace Gap Analysis, you can find gaps of entries regardless of method name.

· Trace Gap Analysis : Sorted list of trace gaps longer than threshold with same thread id

· Time: Time between two trace lines exit of same thread id

· Trace: Actual line from trace file

· Line Number: Line number of the trace entry

· File : File name

13. Click on each row to display actual trace entries

14. By selecting Request Analysis menu, you can find delays in requests

· Request Analysis : Sorted list of requests taken longer than threshold
The following strings are used for detecting requests
– “setRequestURL input [”
– “webcontainer.handleRequest request uri –> ”
– “ws_common: websphereHandleRequest: Request is:”
– “SRTServletRes < finish Exit”
– “ws_common: websphereEndRequest: Ending the request”

· Time: Time between request entry and request completion

· URL: URL of request

· Status Code : HTTP status code
The following strings are used for detecting requests
– “setStatusCode(sc): set to Status code:”
– “TRACE: HTTP/”

· Trace: Actual line from trace file

· Line Number: Line number of the trace entry

· File : File name

15. Click on each row to display actual trace entries

16. Select View -> Options to change options

17. On Basic pane the following options can be changed:

· Default directory for opening files

· Gap Threshold. The value 1 means the tool will analyze gaps larger than 1 second

· Number of lines to display : Number of trace entries before and after each line in lower half of the screen as seen at step 15.

· Verbose : Prints out more information in Console

· Save option : Options will be saved automatically

· Look and feel : User interface configuration

18. Customized gap analysis can be added or modified from Advanced options pane

· ID List : ID list of customized gap search

· Menu name : Menu name under Customized Analysis Menu

· Mnemonic Key : Mnemonic hot key

· Description : description of customized gap search

· Entry keyword : search string for entry

· Exit keyword : search string for exit

· The tool will search for entry and exit keywords to find delays longer than threshold specified in Basic options pane.

· WARNING : Please reopen the file to analyze traces if new keywords are added after traces are already opened and processed.

19. Completed customized analysis will be displayed under Customized Analysis Menu

20. The following is screen shot of a customized gap analysis with Entry keyword of “distSecurityC > initialize Entry” and Exit keyword of “distSecurityC < initialize Exit”.

21. Click on each row to display actual trace entries around the selected entry.

22. Customized Analysis can also be invoked by pop up menu with right mouse button click

23. Product information can be found by selecting Help->About

Download: Trace & Request Analyzer

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s