Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8236214 | 15 | Chris Plummer | P3 | Resolved | Fixed | b02 |
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
Note that
- backported by
-
JDK-8236214 Disable clhsdb initialization of SA javascript support since it will always fail, and will likely be removed soon
-
- Resolved
-
- blocks
-
JDK-8234277 ClhsdbLauncher should enable verbose exceptions and do a better job of detecting SA failures
-
- Resolved
-
- relates to
-
JDK-8244668 Remove SA's javascript support
-
- Resolved
-
-
JDK-8235594 SA javascript support has been broken since 9
-
- Closed
-
-
JDK-8157947 SA: Javascript engine can't access internal packages of jdk.hotspot.agent
-
- Closed
-
-
JDK-8234277 ClhsdbLauncher should enable verbose exceptions and do a better job of detecting SA failures
-
- Resolved
-