Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8324066 "clhsdb jstack" should not by default scan for j.u.c locks because it can be very slow
  3. JDK-8324343

Release Note: `clhsdb jstack` No Longer Scans for `java.util.concurrent` Locks by Default

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Delivered
    • Icon: P4 P4
    • 23
    • 23
    • hotspot

      The `jstack` command in `jhsdb clhsdb` has been modified to scan for `java.util.concurrent` locks only if given the `-l` option. Searching for these locks is a very expensive operation that requires scanning the entire heap. The `jhsdb jstack` and `bin/jstack` commands also have the ability to include this locking information in the output, but do not do so by default.

            cjplummer Chris Plummer
            cjplummer Chris Plummer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: