Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8236062

Disable clhsdb initialization of SA javascript support since it will always fail, and will likely be removed soon

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 14
    • Fix Version/s: 14
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b28

      Backports

        Description

        As described in JDK-8235594, when clhsdb attempts to initialize javascript support, it will always fail. After some discussion, it looks like what is most likely is that we'll soon remove the javascript support. See the following thread:

        http://mail.openjdk.java.net/pipermail/serviceability-dev/2019-December/030038.html

        Before fully removing SA javascript support, a good first step would be to disable any attempt to initialize it, which will get rid of the warning about nashorn going away, and also get rid exception stacktrace mentioned in JDK-8235594 that you see if you first issue the "verbose true" command.

        Note that JDK-8234277 is on hold due to the exception (it will clutter the clhsdb test logs even on passing tests), and the fix I have planned for JDK-8234048 will rely on changes in JDK-8234277 to do a better job of detecting attach failures.

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                cjplummer Chris Plummer
                Reporter:
                cjplummer Chris Plummer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: