JDK-8236062 : Disable clhsdb initialization of SA javascript support since it will always fail, and will likely be removed soon
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: 14
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-12-17
  • Updated: 2020-05-08
  • Resolved: 2019-12-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 14 JDK 15
14 b28Fixed 15Fixed
Related Reports
Blocks :  
Relates :  
Relates :  
Relates :  
Relates :  
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.
Comments
URL: https://hg.openjdk.java.net/jdk/jdk14/rev/7a42c8914389 User: cjplummer Date: 2019-12-18 04:22:46 +0000
18-12-2019