A thread dump is a snapshot of the stacks of all threads in a JVM, and a series of them taken a few seconds apart shows which threads are stuck or consuming time, so they are the standard evidence for analysing slowness. The product offers administrators two supported routes. In the administrative console, the server's runtime page offers a Java Virtual Machine section with a Generate Thread Dump option, which signals the JVM to produce a javacore on the host. In wsadmin, the administrator can obtain the JVM MBean and call its dumpThreads operation, which triggers the same action and is easy to script, so that repeated dumps are taken at set intervals. Options C and E are correct.
The other choices are not thread dump tools. WebSphere Developer Tools, option A, are an Eclipse-based development environment used to build and test applications. The Job Manager, option B, coordinates administrative jobs across multiple environments, and the administrative agent, option D, manages unfederated nodes; neither is a diagnostic collector for thread dumps.
Whichever route is chosen, three to five dumps with an interval of about thirty seconds are normally collected, and these are then analysed with the IBM Thread and Monitor Dump Analyzer to identify blocked threads and contention. The javacore files are written to the profile's root directory.
[Reference: Generating thread dumps (javacore); JVM MBean dumpThreads; Troubleshooting slow application response.]