Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Java Environments 4.1.

Identifying blocked threads

You can identify blocked threads on the Thread Contention (THRDCON) view. On THRDCON you can identify threads that are in blocked state. A blocked state exists when one method is waiting for a Java resource held by another thread in the same JVM.

To identify blocked threads

  1. Select the Thread Contention option on EZJE.
  2. Hyperlink on the Thread Name field for a thread in BLOCKED state to see additional information in on the Thread Detail view (THRDDTLD).
Example

The following figure shows a sample of the THRDCON view with contentions (BLOCKED thread state) in Thread-10, Thread-11, Thread-13, Thread-14, Thread-17:

thrdcon_view.png

 

 In this example, you can hyperlink from Thread-10 to access detailed information on the THRDDTLD view:

thrddtld_view.png

On THRDDTLD, Lock Owner Name shows the line number of the Java class in another thread (Thread-11) where the lock occurred. Blocked Object identifies the object for which the blocked thread (Thread-10) is waiting (java.lang.String@d388acf1).


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*