Examples of analysis modules for WebSphere Application Server problems
To see all the available analyzers for WebSphere® Application Server problems, look at the list of analyzers in the menu on the Launch screen, either under the entry labelled WebSphere
Application Server or (in the package tree) com.ibm.dtfj.analyzer.was. When selecting each analyzer on this list, you can see further information about its function in the Description area near the bottom of the screen.
Generally, this list of available analyzers is continuously growing, as new analyzers are being written and released, so this documentation will not attempt to provide an exhaustive list. We will just mention a few examples, that may serve as a starting point:
- WASBasicInfo: generates a high-level summary of the state of a WebSphere Application Server
process: list the deployed applications, number of active servlets,
number of active EJBs, number of database connections, summary of the thread
pools, etc.
- WASVersion: figures-out the WebSphere version from a WebSphere Application Server dump
- WASThreadIDs: builds a table showing the mapping between the
JVM-level thread IDs and the WebSphere Application Server thread IDs as they appear in a WebSphere Application Server
trace
- WASThreadPoolsBasic: prints all the WebSphere Application Server thread pools, the
number of threads in various states in each pool, and the stack traces
of threads in the pool
- WASSystemManagementBasic: prints the list of remote WebSphere Application Server
processes (servers, node agents, deployment managers) known to the WebSphere Application Server SM subsystem in
this process
- ... and various others