JDK-8023667 : SA: ExceptionBlob and other C2 classes not available in client VM
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: hs25,8,9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2013-08-23
  • Updated: 2018-02-15
  • Resolved: 2014-02-12
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 8 JDK 9
8u162Fixed 9 b04Fixed
Related Reports
Relates :  
JDK-8011888 - sa.js: TypeError: [object JSAdapter] has no such function "__has__"
Description
The following failure was spotted in the 2013.08.22 RT_Baseline nightly.

JDK: Java(TM) SE Runtime Environment 1.8.0 b104 (1.8.0-ea-fastdebug-b104)
VM:  Java HotSpot(TM) 64-Bit Server VM 25.0 b47 (25.0-b47-internal-201308221725.iklam.8023406_build_win_sa-fastdebug)

compiler/ciReplay/TestSA.sh

    This test failed due to "Exception in thread "main"
    java.lang.ExceptionInInitializerError" and "RuntimeException: No type named
    "ExceptionBlob" in database".
Comments
I hit this bug while investigating a bug in 8u11. Why was this not backported to 8?
06-11-2014
JavaScript engine try to initilize couple of C2 specific objects, regardless of type of VM we are running on.
31-01-2014
This failed in JDK 9 RT nightlies Test run URL: http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=352741.JAVASE.NIGHTLY.VM.RT_Baseline.2014-01-27-334&show-limit=0&filter= Host: sunfire001, AMD Opteron 2191 MHz, 2 cores, 4G, Win32 / Windows Server (R) 2008 Standard Options: -server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -XX:ReservedCodeCacheSize=256M RULE compiler/ciReplay/TestSA.sh Exception java.lang.ExceptionInInitializerError RULE compiler/ciReplay/TestSA.sh Exception java.lang.RuntimeException: No type named "ExceptionBlob" in database
29-01-2014
RULE compiler/ciReplay/TestSA.sh Exception sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the core file
28-10-2013
2013.10.14 RT_Baseline nightly Opening core file, please wait... Unable to open core file test_core: Can't attach to the core file sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the core file Test run URL: http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=304634.JAVASE.NIGHTLY.VM.RT_Baseline.2013-10-14-68#JT_HS%20%5B!jfr%5D%20(jtreg)_compiler/ciReplay/TestSA.sh Host: scaaa295, Intel Xeon 2901 MHz, 32 cores, 252G, Linux / Oracle Linux 6.3, x86_64 Options: -client -Xmixed -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -XX:ReservedCodeCacheSize=256M RULE compiler/ciReplay/TestSA.sh sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the core file
16-10-2013
2013:10.14 RT_Baseline nightly Java HotSpot(TM) Server VM warning: increase O_BUFLEN in ostream.hpp -- output truncated Java HotSpot(TM) Server VM warning: increase O_BUFLEN in ostream.hpp -- output truncated Java HotSpot(TM) Server VM warning: increase O_BUFLEN in ostream.hpp -- output truncated java version "1.8.0-ea-fastdebug" Java(TM) SE Runtime Environment (build 1.8.0-ea-fastdebug-b109) Java HotSpot(TM) Server VM (build 25.0-b54-internal-201310121945.hseigel.bug_8024667-fastdebug, mixed mode) /export/local/aurora/sandbox/sca/vmsqe/testbase/jtreg/nightly/rt_baseline/JT_HS/test/compiler/ciReplay/common.sh: line 194: 12427 Aborted (core dumped) ${cmd} > crash.out 2>&1 Opening core file, please wait... Unable to open core file test_core: Can't attach to the core file sun.jvm.hotspot.debugger.DebuggerException: Can't attach to the core file at sun.jvm.hotspot.debugger.linux.LinuxDebuggerLocal.attach0(Native Method) at sun.jvm.hotspot.debugger.linux.LinuxDebuggerLocal.attach(LinuxDebuggerLocal.java:286) at sun.jvm.hotspot.HotSpotAgent.attachDebugger(HotSpotAgent.java:673) at sun.jvm.hotspot.HotSpotAgent.setupDebuggerLinux(HotSpotAgent.java:611) at sun.jvm.hotspot.HotSpotAgent.setupDebugger(HotSpotAgent.java:337) at sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:304) at sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:156) at sun.jvm.hotspot.CLHSDB.attachDebugger(CLHSDB.java:202) at sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:63) at sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:40) Input stream closed. result: Failed. Execution failed: exit code 1 Test run URL: http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=304634.JAVASE.NIGHTLY.VM.RT_Baseline.2013-10-14-68#JT_HS%20%5B!jfr%5D%20(jtreg)_compiler/ciReplay/TestSA.sh Host: scaaa295, Intel Xeon 2901 MHz, 32 cores, 252G, Linux / Oracle Linux 6.3, x86_64 Options: -client -Xmixed -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -XX:ReservedCodeCacheSize=256M
15-10-2013
ILW=MHL=P3, Medium impact as data is not available, happens every time, only on Windows 32bit.
09-10-2013
RULE compiler/ciReplay/TestSA.sh Exception java.lang.RuntimeException: No type named "ExceptionBlob" in database
26-08-2013
moved to hotspot/svc, since execption was rasied by SA. Exception in thread "main" java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:339) at jdk.nashorn.internal.runtime.Context.findClass(Context.java:634) at jdk.nashorn.internal.runtime.NativeJavaPackage.noSuchProperty(NativeJavaPackage.java:205) at jdk.nashorn.internal.runtime.ScriptObject.findGetMethod(ScriptObject.java:1737) at jdk.nashorn.internal.runtime.ScriptObject.lookup(ScriptObject.java:1651) at jdk.nashorn.internal.runtime.linker.NashornLinker.getGuardedInvocation(NashornLinker.java:75) at jdk.internal.dynalink.support.CompositeTypeBasedGuardingDynamicLinker.getGuardedInvocation(CompositeTypeBasedGuardingDynamicLinker.java:176) at jdk.internal.dynalink.support.CompositeGuardingDynamicLinker.getGuardedInvocation(CompositeGuardingDynamicLinker.java:124) at jdk.internal.dynalink.support.LinkerServicesImpl.getGuardedInvocation(LinkerServicesImpl.java:138) at jdk.internal.dynalink.DynamicLinker.relink(DynamicLinker.java:232) at jdk.nashorn.internal.scripts.Script$sa.runScript(sa.js:815) at jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:518) at jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:204) at jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:364) at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:466) at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:450) at jdk.nashorn.api.scripting.NashornScriptEngine.eval(NashornScriptEngine.java:157) at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:249) at sun.jvm.hotspot.utilities.soql.JSJavaScriptEngine.evalReader(JSJavaScriptEngine.java:632) at sun.jvm.hotspot.utilities.soql.JSJavaScriptEngine.loadInitFile(JSJavaScriptEngine.java:477) at sun.jvm.hotspot.utilities.soql.JSJavaScriptEngine.start(JSJavaScriptEngine.java:425) at sun.jvm.hotspot.utilities.soql.JSJavaScriptEngine.start(JSJavaScriptEngine.java:61) at sun.jvm.hotspot.CommandProcessor.postAttach(CommandProcessor.java:1742) at sun.jvm.hotspot.CommandProcessor.<init>(CommandProcessor.java:1780) at sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:98) at sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:40) Caused by: java.lang.RuntimeException: No type named "ExceptionBlob" in database at sun.jvm.hotspot.types.basic.BasicTypeDataBase.lookupType(BasicTypeDataBase.java:85) at sun.jvm.hotspot.HotSpotTypeDataBase.lookupType(HotSpotTypeDataBase.java:134) at sun.jvm.hotspot.types.basic.BasicTypeDataBase.lookupType(BasicTypeDataBase.java:79) at sun.jvm.hotspot.code.ExceptionBlob.initialize(ExceptionBlob.java:45) at sun.jvm.hotspot.code.ExceptionBlob.access$000(ExceptionBlob.java:35) at sun.jvm.hotspot.code.ExceptionBlob$1.update(ExceptionBlob.java:39) at sun.jvm.hotspot.runtime.VM.registerVMInitializedObserver(VM.java:401) at sun.jvm.hotspot.code.ExceptionBlob.<clinit>(ExceptionBlob.java:37) ... 27 more
23-08-2013